From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/7] drm/i915: PCH_NOP suspend/resume
Date: Mon, 8 Apr 2013 20:57:20 +0200 [thread overview]
Message-ID: <20130408185720.GP2228@phenom.ffwll.local> (raw)
In-Reply-To: <20130406174144.GD2228@phenom.ffwll.local>
On Sat, Apr 06, 2013 at 07:41:44PM +0200, Daniel Vetter wrote:
> On Fri, Apr 05, 2013 at 01:12:42PM -0700, Ben Widawsky wrote:
> > More registers we can't write.
> >
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
>
> Fixed up a minor bug (at least I think it's one) in the irq uninstall
> code. Note that this is also run on gpu hangs and resume, so relevant.
>
> Also there's been a little conflict with Paulo's SDE irq handling fix in
> -fixes. I recommend to base all feature work on top of -nightly to avoid
> such issues. If there'll be a conflict when the patch applies only to
> -nightly, but not dinq, I can fix this up when applying.
Ok, I've embarassed myself here a bit and fixed up the ilk irq handler,
which isn't run at all on ivb. I've rectified that again.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-04-08 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 20:12 [PATCH 1/7] drm/i915: Support PCH no display Ben Widawsky
2013-04-05 20:12 ` [PATCH 2/7] drm/i915: PCH_NOP Ben Widawsky
2013-04-05 20:12 ` [PATCH 3/7] drm/i915: Don't touch South Display when PCH_NOP Ben Widawsky
2013-04-05 20:12 ` [PATCH 4/7] drm/i915: PCH_NOP suspend/resume Ben Widawsky
2013-04-06 17:41 ` Daniel Vetter
2013-04-08 18:57 ` Daniel Vetter [this message]
2013-04-05 20:12 ` [PATCH 5/7] drm/i915: Don't wait for PCH on reset Ben Widawsky
2013-04-05 20:12 ` [PATCH 6/7] drm/i915: Set PCH_NOP Ben Widawsky
2013-04-05 20:12 ` [PATCH 7/7] drm/i915: Add a pipeless ivybridge configuration Ben Widawsky
2013-04-06 17:42 ` Daniel Vetter
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=20130408185720.GP2228@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--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.