From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH] drm/i915: fix overlay on i830M Date: Tue, 23 Oct 2012 10:56:46 +0100 Message-ID: <84c8a8$67mfbd@orsmga001.jf.intel.com> References: <1350903355-2102-1-git-send-email-daniel.vetter@ffwll.ch> <20121023091202.GK24005@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0054117407==" Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id E7A8B9F3A3 for ; Tue, 23 Oct 2012 02:57:15 -0700 (PDT) In-Reply-To: <20121023091202.GK24005@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Daniel Vetter , Intel Graphics Development Cc: Daniel Vetter , stable@vger.kernel.org List-Id: intel-gfx@lists.freedesktop.org --===============0054117407== Content-Type: text/plain On Tue, 23 Oct 2012 11:12:02 +0200, Daniel Vetter wrote: > On Mon, Oct 22, 2012 at 12:55:55PM +0200, Daniel Vetter wrote: > > The overlay on the i830M has a peculiar failure mode: It works the > > first time around after boot-up, but consistenly hangs the second time > > it's used. > > > > Chris Wilson has dug out a nice errata: > > > > "1.5.12 Clock Gating Disable for Display Register > > Address Offset: 06200h–06203h > > > > "Bit 3 > > Ovrunit Clock Gating Disable. > > 0 = Clock gating controlled by unit enabling logic > > 1 = Disable clock gating function > > DevALM Errata ALM049: Overlay Clock Gating Must be Disabled: Overlay > > & L2 Cache clock gating must be disabled in order to prevent device > > hangs when turning off overlay.SW must turn off Ovrunit clock gating > > (6200h) and L2 Cache clock gating (C8h)." > > > > Now I've nowhere found that 0xc8 register and hence couldn't apply the > > l2 cache workaround. But I've remembered that part of the magic that > > the OVERLAY_ON/OFF commands are supposed to do is to rearrange cache > > allocations so that the overlay scaler has some scratch space. > > > > And while pondering how that could explain the hang the 2nd time we > > enable the overlay, I've remembered that the old ums overlay code did > > _not_ issue the OVERLAY_OFF cmd. > > > > And indeed, disabling the OFF cmd results in the overlay working > > flawlessly, so I guess we can workaround the lack of the above > > workaround by simply never disabling the overlay engine once it's > > enabled. > > > > v2: Add a comment in the code. > > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=47827 > > Cc: stable@vger.kernel.org > > Signed-off-by: Daniel Vetter > > Tested-by: Rhys If you care to mention that you are not turning off the old w/a in case it has further side-effects, Reviewed-by: Chris Wilson -Chris -- Chris Wilson, Intel Open Source Technology Centre --===============0054117407== 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 --===============0054117407==--