Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 3/4] drm/xe/vf: Custom GuC reset
Date: Tue,  4 Jun 2024 23:22:30 +0200	[thread overview]
Message-ID: <20240604212231.1416-4-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20240604212231.1416-1-michal.wajdeczko@intel.com>

The VF drivers can't trigger real GuC firmware reset using GDRST
register, but for the VF drivers it is sufficient to send VF_RESET
message to reset any VF specific state maintained by the GuC.
Use our existing VF bootstrap function as VF_RESET is part of it.

Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
 drivers/gpu/drm/xe/xe_guc.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
index 086a048876ba..0bf6e01b8910 100644
--- a/drivers/gpu/drm/xe/xe_guc.c
+++ b/drivers/gpu/drm/xe/xe_guc.c
@@ -430,6 +430,9 @@ int xe_guc_reset(struct xe_guc *guc)
 
 	xe_force_wake_assert_held(gt_to_fw(gt), XE_FW_GT);
 
+	if (IS_SRIOV_VF(gt_to_xe(gt)))
+		return xe_gt_sriov_vf_bootstrap(gt);
+
 	xe_mmio_write32(gt, GDRST, GRDOM_GUC);
 
 	ret = xe_mmio_wait32(gt, GDRST, GRDOM_GUC, 0, 5000, &gdrst, false);
-- 
2.43.0


  parent reply	other threads:[~2024-06-04 21:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 21:22 [PATCH 0/4] VF: Custom init and reset steps Michal Wajdeczko
2024-06-04 21:22 ` [PATCH 1/4] drm/xe/vf: Support only GuC/HuC firmwares Michal Wajdeczko
2024-06-06 11:29   ` Piotr Piórkowski
2024-06-04 21:22 ` [PATCH 2/4] drm/xe/vf: Custom uC initialization Michal Wajdeczko
2024-06-06 11:37   ` Piotr Piórkowski
2024-06-06 13:34     ` Michal Wajdeczko
2024-06-04 21:22 ` Michal Wajdeczko [this message]
2024-06-06 11:38   ` [PATCH 3/4] drm/xe/vf: Custom GuC reset Piotr Piórkowski
2024-06-04 21:22 ` [PATCH 4/4] drm/xe/vf: Custom GT restart Michal Wajdeczko
2024-06-06 11:49   ` Piotr Piórkowski
2024-06-05  5:02 ` ✓ CI.Patch_applied: success for VF: Custom init and reset steps Patchwork
2024-06-05  5:02 ` ✓ CI.checkpatch: " Patchwork
2024-06-05  5:03 ` ✓ CI.KUnit: " Patchwork
2024-06-05  5:15 ` ✓ CI.Build: " Patchwork
2024-06-05  5:15 ` ✗ CI.Hooks: failure " Patchwork
2024-06-05  5:17 ` ✓ CI.checksparse: success " Patchwork
2024-06-05  5:44 ` ✓ CI.BAT: " Patchwork
2024-06-05 15:36 ` ✗ CI.FULL: failure " Patchwork
2024-06-06 13:58   ` Michal Wajdeczko

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=20240604212231.1416-4-michal.wajdeczko@intel.com \
    --to=michal.wajdeczko@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