From: Eric Anholt <eric.anholt@intel.com>
To: "Zou, Nanhai" <nanhai.zou@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Patch 5/5] multiple ring buffer support, fix a irq enable logic for BSD
Date: Mon, 19 Apr 2010 10:25:11 -0700 [thread overview]
Message-ID: <87bpdfmk20.fsf@pollan.anholt.net> (raw)
In-Reply-To: <41EFD7A46E18724CAB128DAD007334800270C6CA60@shsmsx502.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1269 bytes --]
On Mon, 19 Apr 2010 09:34:42 +0800, "Zou, Nanhai" <nanhai.zou@intel.com> wrote:
> >>-----Original Message-----
> >>From: Anholt, Eric
> >>Sent: 2010年4月13日 2:29
> >>To: Zou, Nanhai; intel-gfx@lists.freedesktop.org
> >>Subject: Re: [Intel-gfx] [Patch 5/5] multiple ring buffer support, fix a irq
> >>enable logic for BSD
> >>
> >>On Wed, 7 Apr 2010 14:28:39 +0800, "Zou, Nanhai" <nanhai.zou@intel.com> wrote:
> >>> Fix the BSD ring related IRQ logic on Ironlake.
> >>> Without this patch, we sometimes see IRQ lost
> >>> When playing H.264 content.
> >>
> >>This patch looks crazy. Why do we need to do this? How did you come up
> >>with it? What prevents races between IIR clear and IER or IMR enable (if
> >>that's what the IIR clear is about).
> >>
>
> Yes, it looks a little strange.
> However HW spec from VCG do says IIR should be cleared before enable and disable interrupt.
> We thought this patch fixed the interrupt lost issue seen when playing movie. But now we found it just make the issue much harder to reproduce, so ignore this patch until we found a real fix.
Before enable, sure, that makes sense -- otherwise you'd trigger an
interrupt right away when you know you don't need it. But we do
unmasking, not enabling.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2010-04-19 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32606542045FF34BA04F9D5BB0CB6BB5A53A282E@shzsmsx502.ccr.corp.intel.com>
[not found] ` <87d3y45xuk.fsf@pollan.anholt.net>
2010-04-19 1:34 ` [Patch 5/5] multiple ring buffer support, fix a irq enable logic for BSD Zou, Nanhai
2010-04-19 17:25 ` Eric Anholt [this message]
2010-04-23 8:36 ` Zou, Nanhai
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=87bpdfmk20.fsf@pollan.anholt.net \
--to=eric.anholt@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nanhai.zou@intel.com \
/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.