public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 5/5] drm/i915: Simplify intel_init_ring_buffer prototype
Date: Wed, 6 Jul 2016 13:38:49 +0100	[thread overview]
Message-ID: <577CFBD9.7000300@linux.intel.com> (raw)
In-Reply-To: <20160706105847.GK15134@nuc-i3427.alporthouse.com>


On 06/07/16 11:58, Chris Wilson wrote:
> On Wed, Jul 06, 2016 at 11:52:11AM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Engine contains dev_priv so need to pass it in.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> ---
>>   drivers/gpu/drm/i915/intel_ringbuffer.c | 18 ++++++++----------
>>   1 file changed, 8 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
>> index 6b24c1642d84..26fe312005d1 100644
>> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
>> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
>> @@ -2167,21 +2167,19 @@ static void intel_ring_context_unpin(struct i915_gem_context *ctx,
>>   	i915_gem_context_unreference(ctx);
>>   }
>>
>> -static int intel_init_ring_buffer(struct drm_device *dev,
>> -				  struct intel_engine_cs *engine)
>> +static int intel_init_ring_buffer(struct intel_engine_cs *engine)
>>   {
>> -	struct drm_i915_private *dev_priv = to_i915(dev);
>> +	struct drm_i915_private *dev_priv = engine->i915;
>>   	struct intel_ringbuffer *ringbuf;
>>   	int ret;
>>
>>   	WARN_ON(engine->buffer);
>>
>> -	engine->i915 = dev_priv;
>>   	INIT_LIST_HEAD(&engine->active_list);
>>   	INIT_LIST_HEAD(&engine->request_list);
>>   	INIT_LIST_HEAD(&engine->execlist_queue);
>>   	INIT_LIST_HEAD(&engine->buffers);
>
> Patch 6/5, Move all the common init code to the dispatch?

What do you mean by dispatch?

But yes, that could be the next step.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-06 12:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 10:52 [PATCH 1/5] drm/i915: unify first-stage engine struct setup Tvrtko Ursulin
2016-07-06 10:52 ` [PATCH 2/5] drm/i915: Prepare for engine init unification Tvrtko Ursulin
2016-07-06 10:52 ` [PATCH 3/5] drm/i915: Unify engine init loop Tvrtko Ursulin
2016-07-06 11:05   ` Chris Wilson
2016-07-06 12:42     ` Tvrtko Ursulin
2016-07-06 10:52 ` [PATCH 4/5] drm/i915: Make more use of the shared engine irq setup Tvrtko Ursulin
2016-07-06 10:52 ` [PATCH 5/5] drm/i915: Simplify intel_init_ring_buffer prototype Tvrtko Ursulin
2016-07-06 10:58   ` Chris Wilson
2016-07-06 12:38     ` Tvrtko Ursulin [this message]
2016-07-06 12:47       ` Chris Wilson
2016-07-06 11:23 ` ✗ Ro.CI.BAT: failure for series starting with [1/5] drm/i915: unify first-stage engine struct setup Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2016-07-01 16:47 [PATCH 1/5] " Tvrtko Ursulin
2016-07-01 16:47 ` [PATCH 5/5] drm/i915: Simplify intel_init_ring_buffer prototype Tvrtko Ursulin
2016-07-13 12:30   ` Daniel Vetter

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=577CFBD9.7000300@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    /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