From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Anholt 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 Message-ID: <87bpdfmk20.fsf@pollan.anholt.net> References: <32606542045FF34BA04F9D5BB0CB6BB5A53A282E@shzsmsx502.ccr.corp.intel.com> <87d3y45xuk.fsf@pollan.anholt.net> <41EFD7A46E18724CAB128DAD007334800270C6CA60@shsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0203706347==" Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id 8560E9EA09 for ; Mon, 19 Apr 2010 10:25:53 -0700 (PDT) In-Reply-To: <41EFD7A46E18724CAB128DAD007334800270C6CA60@shsmsx502.ccr.corp.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: intel-gfx-bounces@lists.freedesktop.org Errors-To: intel-gfx-bounces@lists.freedesktop.org To: "Zou, Nanhai" , "intel-gfx@lists.freedesktop.org" List-Id: intel-gfx@lists.freedesktop.org --===============0203706347== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Mon, 19 Apr 2010 09:34:42 +0800, "Zou, Nanhai" wr= ote: > >>-----Original Message----- > >>From: Anholt, Eric > >>Sent: 2010=E5=B9=B44=E6=9C=8813=E6=97=A5 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" = 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). > >> >=20 > Yes, it looks a little strange.=20 > 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 mo= vie. But now we found it just make the issue much harder to reproduce, so i= gnore 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. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvMkfcACgkQHUdvYGzw6vcfiQCdFnYXCRpL6vI85Xcqich2czGZ DzEAn0WiAaFPLJooc0Z6DkMGHP3PmtME =Zv+R -----END PGP SIGNATURE----- --=-=-=-- --===============0203706347== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============0203706347==--