From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/5] drm/i915: Simplify cleanup path in intel_engines_init
Date: Thu, 16 Feb 2017 12:23:22 +0000 [thread overview]
Message-ID: <20170216122325.31391-3-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20170216122325.31391-1-tvrtko.ursulin@linux.intel.com>
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
We can call the engine cleanup vfunc instead of duplicating the
decision making here.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/intel_engine_cs.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
index 538d845d7251..012ac9483491 100644
--- a/drivers/gpu/drm/i915/intel_engine_cs.c
+++ b/drivers/gpu/drm/i915/intel_engine_cs.c
@@ -210,10 +210,8 @@ int intel_engines_init(struct drm_i915_private *dev_priv)
for_each_engine(engine, dev_priv, id) {
if (id >= err_id)
kfree(engine);
- else if (i915.enable_execlists)
- intel_logical_ring_cleanup(engine);
else
- intel_engine_cleanup(engine);
+ dev_priv->gt.cleanup_engine(engine);
}
return err;
}
--
2.9.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-16 12:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 12:23 [PATCH 0/5] Assorted engine tidy Tvrtko Ursulin
2017-02-16 12:23 ` [PATCH 1/5] drm/i915: Make int __intel_ring_space static Tvrtko Ursulin
2017-02-16 13:12 ` Chris Wilson
2017-02-16 12:23 ` Tvrtko Ursulin [this message]
2017-02-16 13:15 ` [PATCH 2/5] drm/i915: Simplify cleanup path in intel_engines_init Chris Wilson
2017-02-16 12:23 ` [PATCH 3/5] drm/i915: Move common workaround code to intel_engine_cs Tvrtko Ursulin
2017-02-16 13:18 ` Chris Wilson
2017-02-16 12:23 ` [PATCH 4/5] drm/i915: Tidy workaround batch buffer emission Tvrtko Ursulin
2017-02-16 13:20 ` Chris Wilson
2017-02-16 13:23 ` Tvrtko Ursulin
2017-02-16 13:28 ` Chris Wilson
2017-02-16 13:47 ` Tvrtko Ursulin
2017-02-16 13:51 ` [PATCH v4 1/2] " Tvrtko Ursulin
2017-02-16 13:54 ` [PATCH v5 " Tvrtko Ursulin
2017-02-16 14:03 ` Chris Wilson
2017-02-17 7:58 ` [PATCH v6] " Tvrtko Ursulin
2017-02-17 8:16 ` Chris Wilson
2017-02-16 12:23 ` [PATCH 5/5] drm/i915: Consolidate gen8_emit_pipe_control Tvrtko Ursulin
2017-02-16 18:22 ` ✓ Fi.CI.BAT: success for Assorted engine tidy (rev3) Patchwork
2017-02-17 8:22 ` ✗ Fi.CI.BAT: failure for Assorted engine tidy (rev4) Patchwork
2017-02-17 11:50 ` Tvrtko Ursulin
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=20170216122325.31391-3-tvrtko.ursulin@linux.intel.com \
--to=tursulin@ursulin.net \
--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