dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Keith Packard <keithp@keithp.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: mark display port DPMS state as ON when enabling output
Date: Sun, 03 Oct 2010 22:05:13 +0100	[thread overview]
Message-ID: <89k77n$p47jkc@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1286138029-3728-1-git-send-email-keithp@keithp.com>

On Sun,  3 Oct 2010 13:33:49 -0700, Keith Packard <keithp@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 sets the DPMS state to ON when the output is enabled.

It appears that all users (crtc and encoders) are tracking dpms_mode, in
one form or another. Should we move this to core?

Is there any hardware that requires notification even when there is no
change?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2010-10-03 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 20:33 [PATCH] drm/i915: mark display port DPMS state as 'ON' when enabling output Keith Packard
2010-10-03 21:05 ` Chris Wilson [this message]
2010-10-03 23:06   ` [PATCH] drm/i915: mark display port DPMS state as ON " Keith Packard
2010-10-04  9:17     ` [Intel-gfx] " Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='89k77n$p47jkc@fmsmga001.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox