public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: rip out sanitize_pm again
Date: Thu, 26 Jul 2012 13:38:42 +0200	[thread overview]
Message-ID: <20120726113842.GD5326@phenom.ffwll.local> (raw)
In-Reply-To: <1343297700_2011@CP5-2952>

On Thu, Jul 26, 2012 at 11:14:59AM +0100, Chris Wilson wrote:
> On Thu, 26 Jul 2012 11:50:05 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > We believe to have squashed all issues around the gen6+ rps interrupt
> > generation and why the gpu sometimes got stuck. With that cleared up,
> > there's no user left for the sanitize_pm infrastructure, so let's just
> > rip it out.
> > 
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> I would amend the changelog to include
> 'intel_reg_write 0xa014 0x13070000' as the w/a if we find ourselves
> stuck again.
> 
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
I've applied both patches (with the w/a note added) to dinq, let's see
what happens. Thanks for the review.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      reply	other threads:[~2012-07-26 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 19:32 [PATCH] [CFT] drm/i915: Only set the down rps limit when at the loweset frequency Daniel Vetter
2012-07-25 22:09 ` Chris Wilson
2012-07-26  9:16   ` Daniel Vetter
2012-07-26  9:23     ` Chris Wilson
2012-07-26  9:37       ` Chris Wilson
2012-07-26  9:50         ` [PATCH] drm/i915: rip out sanitize_pm again Daniel Vetter
2012-07-26 10:14           ` Chris Wilson
2012-07-26 11:38             ` Daniel Vetter [this message]

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=20120726113842.GD5326@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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