summaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/cpu/Makefile
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2015-01-21 08:45:22 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2015-01-22 06:11:39 +0100
commitb7703726251191cd9f3ef3a80b2d9667901eec95 (patch)
treee2398efa8afa5d991cc1d19d664c8065098d81ea /arch/x86/kernel/cpu/Makefile
parentdrm/probe-helper: don't lose hotplug event (diff)
downloadlinux-b7703726251191cd9f3ef3a80b2d9667901eec95.tar.xz
linux-b7703726251191cd9f3ef3a80b2d9667901eec95.zip
drm/probe-helper: clamp unknown connector status in the poll work
On some chipset we try to avoid possibly invasive output detection methods (like load detect which can cause flickering elsewhere) in the output poll work. Drivers could hence return unknown when a previous full ->detect call returned a different state. This change will generate a hotplug event, forcing userspace to do a full scan. This in turn updates the connector->status field so that we will _again_ get a state change when the hotplug work re-runs in 10 seconds. To avoid this ping-pong loop detect this situation and clamp the connector state to the old value. Patch is inspired by a patch from Knut Peterson. Knut's patch completely ignored connector state changes if either the old or new status was unknown, which seemed to be a bit too agressive to me. v2: Rebased onto the drm_probe_helper.c extraction. References: http://lists.freedesktop.org/archives/dri-devel/2012-August/025975.html Cc: Knut Petersen <Knut_Petersen@t-online.de> Cc: Alex Deucher <alexander.deucher@amd.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Acked-by: Alex Deucher <alexander.deucher@amd.com> Cc: Rob Clark <robdclark@gmail.com> Reviewed-by: Rob Clark <robdclark@gmail.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'arch/x86/kernel/cpu/Makefile')
0 files changed, 0 insertions, 0 deletions