public inbox for intel-gfx@lists.freedesktop.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: stable@kernel.org
Subject: Re: [PATCH] drm/i915: Sanitize the output registers after resume
Date: Tue, 12 Apr 2011 19:01:11 +0100	[thread overview]
Message-ID: <b7da2f$r2hjva@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <yunoc4bpeib.fsf@aiko.keithp.com>

On Tue, 12 Apr 2011 10:26:36 -0700, Keith Packard <keithp@keithp.com> wrote:
> On Tue, 12 Apr 2011 18:06:51 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 
> > This patch rearranges the code we already have to clear up the
> > conflicting state upon init and calls it from reset (which is called
> > after we have lost control of the hardware, i.e. along both the boot and
> > resume paths) instead.
> 
> Note that intel_sanitize_modesetting does not do anything on PCH
> hardware yet. Otherwise, this looks like a reasonable plan.

Yes, at the moment the only scenario we've discovered is where the BIOS
sets up a conflicting pipe<->plane mapping, which is only possible before
PCH.

If we go hunting, we can probably find many more. :|
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-04-12 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 17:06 [PATCH] drm/i915: Sanitize the output registers after resume Chris Wilson
2011-04-12 17:10 ` Chris Wilson
2011-04-12 17:26 ` Keith Packard
2011-04-12 18:01   ` Chris Wilson [this message]
2011-04-13  0:00 ` Jesse Barnes
2011-04-13  6:53   ` 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='b7da2f$r2hjva@fmsmga001.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    --cc=stable@kernel.org \
    /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