From: Daniel Vetter <daniel@ffwll.ch>
To: "Mateo Lozano, Oscar" <oscar.mateo@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 6/6] drm/i915: Kick start the rings
Date: Tue, 22 Apr 2014 21:25:20 +0200 [thread overview]
Message-ID: <20140422192520.GC10722@phenom.ffwll.local> (raw)
In-Reply-To: <92648605EABDA246B775AAB04C95A7A3012DA849@IRSMSX103.ger.corp.intel.com>
On Tue, Apr 22, 2014 at 01:06:45PM +0000, Mateo Lozano, Oscar wrote:
> > Subject: [Intel-gfx] [PATCH 6/6] drm/i915: Kick start the rings
> >
> > On g4x, we have an issue where the register write to setup the rings do not
> > always take. However, it appears that the current check also passes only by
> > chance, a second reading of the register returns a different broekn value - but
> > the GPU appears to function. Based on that observation, lets try feeding a nop
> > into the ring and seeing if it advances as part of our startup sanity checks.
> >
> > References: https://bugs.freedesktop.org/show_bug.cgi?id=76554
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > ---
> > drivers/gpu/drm/i915/intel_ringbuffer.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index a8c73a0d935d..bc52645fa8d5 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -514,10 +514,14 @@ static int init_ring_common(struct intel_ring_buffer
> > *ring)
> > ((ring->size - PAGE_SIZE) & RING_NR_PAGES)
> > | RING_VALID);
> >
> > + iowrite32(MI_NOOP, ring->virtual_start + 0);
> > + iowrite32(MI_NOOP, ring->virtual_start + 4);
> > + ring->write_tail(ring, 8);
>
> Maybe add a comment in the code about why we are doing this? (otherwise, it looks a bit magical)
Yeah, this is a bit too much magic. Also it looks like it doesn't really
help the bug report with his gm45, so I think I'll punt on this one for
now.
All other patches merged with the 2 small suggestions from Oscar applied
while merging. Thanks for patches&review.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-04-22 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 8:19 [PATCH 1/6] drm/i915: Replace hardcoded cacheline size with macro Chris Wilson
2014-04-09 8:19 ` [PATCH 2/6] drm/i915: Preserve ring buffers objects across resume Chris Wilson
2014-04-22 12:56 ` Mateo Lozano, Oscar
2014-04-09 8:19 ` [PATCH 3/6] drm/i915: Allow the module to load even if we fail to setup rings Chris Wilson
2014-04-22 12:57 ` Mateo Lozano, Oscar
2014-04-09 8:19 ` [PATCH 4/6] drm/i915: Mark device as wedged if we fail to resume Chris Wilson
2014-04-22 13:04 ` Mateo Lozano, Oscar
2014-04-09 8:19 ` [PATCH 5/6] drm/i915: Include a little more information about why ring init fails Chris Wilson
2014-04-22 13:04 ` Mateo Lozano, Oscar
2014-04-09 8:19 ` [PATCH 6/6] drm/i915: Kick start the rings Chris Wilson
2014-04-22 13:06 ` Mateo Lozano, Oscar
2014-04-22 19:25 ` Daniel Vetter [this message]
2014-04-22 12:35 ` [PATCH 1/6] drm/i915: Replace hardcoded cacheline size with macro Mateo Lozano, Oscar
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=20140422192520.GC10722@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox