On Sun, 03 Oct 2010 16:06:07 -0700, Keith Packard wrote:
> On Sun, 03 Oct 2010 22:05:13 +0100, Chris Wilson 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
On Sun, 03 Oct 2010 16:06:07 -0700, Keith Packard wrote:
> On Sun, 03 Oct 2010 22:05:13 +0100, Chris Wilson
> 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 prefe
On Sun, 3 Oct 2010 13:33:49 -0700, Keith Packard 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 sets the DPMS s
On Sun, 03 Oct 2010 22:05:13 +0100, Chris Wilson
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 that requires notificati
On Sun, 03 Oct 2010 22:05:13 +0100, Chris Wilson
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 that requires notificati
On Sun, 3 Oct 2010 13:33:49 -0700, Keith Packard 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 sets the DPMS s
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 Packa
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 Packa
