[PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-06 Thread Daniel Vetter
On Thu, Jun 6, 2013 at 9:49 AM, Chris Wilson wrote: > On Thu, Jun 06, 2013 at 12:17:26AM +0200, Daniel Vetter wrote: >> 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 h

[PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-06 Thread Chris Wilson
On Thu, Jun 06, 2013 at 12:17:26AM +0200, Daniel Vetter wrote: > 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 re

[PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-06 Thread Alex Deucher
On Thu, Jun 6, 2013 at 3:49 AM, Chris Wilson wrote: > On Thu, Jun 06, 2013 at 12:17:26AM +0200, Daniel Vetter wrote: >> 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 h

Re: [PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-06 Thread Alex Deucher
On Thu, Jun 6, 2013 at 3:49 AM, Chris Wilson wrote: > On Thu, Jun 06, 2013 at 12:17:26AM +0200, Daniel Vetter wrote: >> 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 he

Re: [PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-06 Thread Daniel Vetter
On Thu, Jun 6, 2013 at 9:49 AM, Chris Wilson wrote: > On Thu, Jun 06, 2013 at 12:17:26AM +0200, Daniel Vetter wrote: >> 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 he

Re: [PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-06 Thread Chris Wilson
On Thu, Jun 06, 2013 at 12:17:26AM +0200, Daniel Vetter wrote: > 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 re

[PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-06 Thread Daniel Vetter
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, f

[PATCH 2/2] drm/crtc-helper: clamp unknown connector status in the poll work

2013-06-05 Thread Daniel Vetter
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, f