Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [PATCH 1/1] drm/xe/guc: Fix missing topology init
Date: Tue, 27 Feb 2024 08:49:22 -0800	[thread overview]
Message-ID: <20240227164922.281346-2-zhanjun.dong@intel.com> (raw)
In-Reply-To: <20240227164922.281346-1-zhanjun.dong@intel.com>

init_steering_dss need topology dss mask to be init ahead.
Fixed by moving xe_gt_topology_init ahead of xe_gt_mcr_init

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
---
 drivers/gpu/drm/xe/xe_gt.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_gt.c b/drivers/gpu/drm/xe/xe_gt.c
index 45646d3aea2d..85408e7a932b 100644
--- a/drivers/gpu/drm/xe/xe_gt.c
+++ b/drivers/gpu/drm/xe/xe_gt.c
@@ -315,8 +315,6 @@ int xe_gt_init_early(struct xe_gt *gt)
 	if (err)
 		return err;
 
-	xe_gt_topology_init(gt);
-
 	err = xe_force_wake_put(gt_to_fw(gt), XE_FW_GT);
 	if (err)
 		return err;
@@ -503,6 +501,7 @@ int xe_gt_init_hwconfig(struct xe_gt *gt)
 	if (err)
 		goto out;
 
+	xe_gt_topology_init(gt);
 	xe_gt_mcr_init(gt);
 	xe_pat_init(gt);
 
-- 
2.34.1


  reply	other threads:[~2024-02-27 16:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 16:49 [PATCH 0/1] drm/xe/guc: Fix missing topology init Zhanjun Dong
2024-02-27 16:49 ` Zhanjun Dong [this message]
2024-02-27 20:38   ` [PATCH 1/1] " Matt Roper
2024-02-28 22:48     ` Lucas De Marchi
2024-02-27 16:54 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-27 16:54 ` ✓ CI.checkpatch: " Patchwork
2024-02-27 16:56 ` ✓ CI.KUnit: " Patchwork
2024-02-27 17:07 ` ✓ CI.Build: " Patchwork
2024-02-27 17:08 ` ✓ CI.Hooks: " Patchwork
2024-02-27 17:10 ` ✓ CI.checksparse: " Patchwork
2024-02-27 17:30 ` ✓ CI.BAT: " 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=20240227164922.281346-2-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=intel-xe@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