Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: [PATCH 1/5] drm/i915: Split i915_gem_init_hw into GT and i915 parts
Date: Wed, 24 Jul 2019 11:07:12 +0100	[thread overview]
Message-ID: <20190724100716.10731-1-tvrtko.ursulin@linux.intel.com> (raw)

From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

One part of the earlier upstream refactoring got undone in the meantime.

Put it back into desirable state by restoring the split between intel_gt
and i915 initialization.

Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
 drivers/gpu/drm/i915/i915_gem.c | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 01dd0d1d9bf6..272e008c55ef 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -1193,13 +1193,12 @@ static void init_unused_rings(struct intel_gt *gt)
 	}
 }
 
-int i915_gem_init_hw(struct drm_i915_private *i915)
+static int init_hw(struct intel_gt *gt)
 {
-	struct intel_uncore *uncore = &i915->uncore;
-	struct intel_gt *gt = &i915->gt;
+	struct drm_i915_private *i915 = gt->i915;
+	struct intel_uncore *uncore = gt->uncore;
 	int ret;
 
-	BUG_ON(!i915->kernel_context);
 	ret = intel_gt_terminally_wedged(gt);
 	if (ret)
 		return ret;
@@ -1261,6 +1260,19 @@ int i915_gem_init_hw(struct drm_i915_private *i915)
 	return ret;
 }
 
+int i915_gem_init_hw(struct drm_i915_private *i915)
+{
+	int ret;
+
+	BUG_ON(!i915->kernel_context);
+
+	ret = init_hw(&i915->gt);
+
+	intel_engines_set_scheduler_caps(i915);
+
+	return ret;
+}
+
 static int __intel_engines_record_defaults(struct drm_i915_private *i915)
 {
 	struct intel_engine_cs *engine;
-- 
2.20.1

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

             reply	other threads:[~2019-07-24 10:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 10:07 Tvrtko Ursulin [this message]
2019-07-24 10:07 ` [PATCH 2/5] drm/i915: Avoid one round-tip through global i915 when getting to gt Tvrtko Ursulin
2019-07-24 10:14   ` Chris Wilson
2019-07-24 10:32     ` Tvrtko Ursulin
2019-07-24 10:07 ` [PATCH 3/5] drm/i915: Make wait_for_timelines take struct intel_gt Tvrtko Ursulin
2019-07-24 10:07 ` [PATCH 4/5] drm/i915: Avoid round-trip via i915 in intel_gt_park Tvrtko Ursulin
2019-07-24 10:07 ` [PATCH 5/5] drm/i915: Make pm_notify take intel_gt Tvrtko Ursulin
2019-07-24 10:41 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915: Split i915_gem_init_hw into GT and i915 parts Patchwork
2019-07-24 12:31 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-07-24 13:00 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915: Split i915_gem_init_hw into GT and i915 parts (rev2) Patchwork
2019-07-24 15:53 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-24 18:18 ` ✓ 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=20190724100716.10731-1-tvrtko.ursulin@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --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