From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: dont enable FDI & transcoder interrupts after all
Date: Sat, 12 Feb 2011 11:23:26 +0000 [thread overview]
Message-ID: <0d30dc$l287qa@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1297464291-3761-1-git-send-email-jbarnes@virtuousgeek.org>
On Fri, 11 Feb 2011 14:44:51 -0800, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> We can enable some safely, but FDI and transcoder interrupts can occur
> and block other interrupts from being detected (like port hotplug
> events). So keep them disabled by default (they can be re-enabled for
> debugging display bringup, but should generally be off).
I've queued this to -fixes. I want to try and sync up painlessly with
linus/master before pushing to the public tree though. I hear most of the
upstream suspend/resume and wifi woes are now abating...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2011-02-12 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 22:44 [PATCH] drm/i915: don't enable FDI & transcoder interrupts after all Jesse Barnes
2011-02-12 11:23 ` Chris Wilson [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='0d30dc$l287qa@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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