From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Setup the RCS ring prior to execution
Date: Thu, 18 Apr 2019 16:10:33 +0100 [thread overview]
Message-ID: <f045a5e6-2597-97e1-8f1e-5630aa8e0503@linux.intel.com> (raw)
In-Reply-To: <20190418132720.3716-2-chris@chris-wilson.co.uk>
On 18/04/2019 14:27, Chris Wilson wrote:
> We need to set the various ring registers prior to restarting the
> engine, or else we may restart it after reset/resume in an ill-defined
> state.
>
> Reported-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/intel_ringbuffer.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> index 00bd9eeb053d..3844581f622c 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> @@ -831,9 +831,6 @@ static int intel_rcs_ctx_init(struct i915_request *rq)
> static int init_render_ring(struct intel_engine_cs *engine)
> {
> struct drm_i915_private *dev_priv = engine->i915;
> - int ret = init_ring_common(engine);
> - if (ret)
> - return ret;
>
> /* WaTimedSingleVertexDispatch:cl,bw,ctg,elk,ilk,snb */
> if (IS_GEN_RANGE(dev_priv, 4, 6))
> @@ -873,7 +870,7 @@ static int init_render_ring(struct intel_engine_cs *engine)
> if (IS_GEN_RANGE(dev_priv, 6, 7))
> I915_WRITE(INSTPM, _MASKED_BIT_ENABLE(INSTPM_FORCE_ORDERING));
>
> - return 0;
> + return init_ring_common(engine);
> }
>
> static void cancel_requests(struct intel_engine_cs *engine)
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-18 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 13:27 [PATCH 1/2] drm/i915: Stop overwriting RING_IMR in rcs resume Chris Wilson
2019-04-18 13:27 ` [PATCH 2/2] drm/i915: Setup the RCS ring prior to execution Chris Wilson
2019-04-18 15:10 ` Tvrtko Ursulin [this message]
2019-04-18 14:34 ` [PATCH 1/2] drm/i915: Stop overwriting RING_IMR in rcs resume Tvrtko Ursulin
2019-04-18 14:59 ` Chris Wilson
2019-04-18 15:08 ` Tvrtko Ursulin
2019-04-18 15:14 ` Chris Wilson
2019-04-18 16:30 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2019-04-18 18:07 ` ✓ Fi.CI.IGT: " Patchwork
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=f045a5e6-2597-97e1-8f1e-5630aa8e0503@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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