All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Simplify interrupt processing for IvyBridge
Date: Thu, 10 May 2012 11:56:24 +0200	[thread overview]
Message-ID: <20120510095624.GE4867@phenom.ffwll.local> (raw)
In-Reply-To: <1336596344-3523-2-git-send-email-chris@chris-wilson.co.uk>

On Wed, May 09, 2012 at 09:45:44PM +0100, Chris Wilson wrote:
> We can take advantage that the PCH_IIR is a subordinate register to
> reduce one of the required IIR reads, and that we only need to clear
> interrupts handled to reduce the writes. And by simply tidying the code
> we can reduce the line count and hopefully make it more readable.
> 
> v2: Split out the bugfix from the refactoring.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Both patches queued for -next, thanks.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-05-10  9:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  8:52 [PATCH 1/2] drm/i915: Support pageflipping interrupts for all 3-pipes on IVB Chris Wilson
2012-05-02  8:52 ` [PATCH 2/2] drm/i915: Simplify the IVB interrupt handler Chris Wilson
2012-05-06 15:37   ` Daniel Vetter
2012-05-06 15:44     ` Chris Wilson
2012-05-09 20:45     ` [PATCH 1/2] drm/i915: Avoid a double-read of PCH_IIR during interrupt handling Chris Wilson
2012-05-09 20:45       ` [PATCH 2/2] drm/i915: Simplify interrupt processing for IvyBridge Chris Wilson
2012-05-10  9:56         ` Daniel Vetter [this message]
2012-05-02 19:46 ` [PATCH 1/2] drm/i915: Support pageflipping interrupts for all 3-pipes on IVB Jesse Barnes
2012-05-06 15:34   ` Daniel Vetter
2012-05-06 16:30     ` Jesse Barnes

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=20120510095624.GE4867@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.