On Sun, 03 Oct 2010 16:06:07 -0700, Keith Packard kei...@keithp.com wrote:
On Sun, 03 Oct 2010 22:05:13 +0100, Chris Wilson ch...@chris-wilson.co.uk
wrote:
It appears that all users (crtc and encoders) are tracking dpms_mode, in
one form or another. Should we move this to core?
Sounds
The display port DPMS state is tracked internally in the display port
driver so that when a hotplug event comes along, the driver can know
whether to try retraining the link. This doesn't work well if the
driver never sets the DPMS state to ON when the output is enabled.
Signed-off-by: Keith
On Sun, 3 Oct 2010 13:33:49 -0700, Keith Packard kei...@keithp.com wrote:
The display port DPMS state is tracked internally in the display port
driver so that when a hotplug event comes along, the driver can know
whether to try retraining the link. This doesn't work well if the
driver never
On Sun, 03 Oct 2010 22:05:13 +0100, Chris Wilson ch...@chris-wilson.co.uk
wrote:
It appears that all users (crtc and encoders) are tracking dpms_mode, in
one form or another. Should we move this to core?
Sounds like a good idea. Would you prefer to do that yourself?
Is there any hardware
