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 v16 6/7] drm/xe/guc: Add dss conversion from group/instance ID
Date: Mon, 19 Aug 2024 19:11:41 -0700	[thread overview]
Message-ID: <20240820021142.436536-7-zhanjun.dong@intel.com> (raw)
In-Reply-To: <20240820021142.436536-1-zhanjun.dong@intel.com>

Add dss conversion from group/instance ID.

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
---
 drivers/gpu/drm/xe/xe_gt_mcr.c | 11 +++++++++++
 drivers/gpu/drm/xe/xe_gt_mcr.h |  1 +
 2 files changed, 12 insertions(+)

diff --git a/drivers/gpu/drm/xe/xe_gt_mcr.c b/drivers/gpu/drm/xe/xe_gt_mcr.c
index 7d7bd0be6233..eff9468ca371 100644
--- a/drivers/gpu/drm/xe/xe_gt_mcr.c
+++ b/drivers/gpu/drm/xe/xe_gt_mcr.c
@@ -352,6 +352,17 @@ void xe_gt_mcr_get_dss_steering(struct xe_gt *gt, unsigned int dss, u16 *group,
 	*instance = dss % gt->steering_dss_per_grp;
 }
 
+/**
+ * xe_gt_mcr_steering_id_to_dss - Get DSS ID from group/instance steering
+ * @gt: GT structure
+ * @group: steering group ID
+ * @instance: steering instance ID
+ */
+u32 xe_gt_mcr_steering_id_to_dss(struct xe_gt *gt, u16 group, u16 instance)
+{
+	return group * dss_per_group(gt) + instance;
+}
+
 static void init_steering_dss(struct xe_gt *gt)
 {
 	gt->steering_dss_per_grp = dss_per_group(gt);
diff --git a/drivers/gpu/drm/xe/xe_gt_mcr.h b/drivers/gpu/drm/xe/xe_gt_mcr.h
index 8d119a0d5493..3c84b20b10c9 100644
--- a/drivers/gpu/drm/xe/xe_gt_mcr.h
+++ b/drivers/gpu/drm/xe/xe_gt_mcr.h
@@ -28,6 +28,7 @@ void xe_gt_mcr_multicast_write(struct xe_gt *gt, struct xe_reg_mcr mcr_reg,
 
 void xe_gt_mcr_steering_dump(struct xe_gt *gt, struct drm_printer *p);
 void xe_gt_mcr_get_dss_steering(struct xe_gt *gt, unsigned int dss, u16 *group, u16 *instance);
+u32 xe_gt_mcr_steering_id_to_dss(struct xe_gt *gt, u16 group, u16 instance);
 
 /*
  * Loop over each DSS and determine the group and instance IDs that
-- 
2.34.1


  parent reply	other threads:[~2024-08-20  2:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  2:11 [PATCH v16 0/7] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-08-20  2:11 ` [PATCH v16 1/7] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-08-27 20:30   ` Teres Alexis, Alan Previn
2024-08-27 22:29     ` Dong, Zhanjun
2024-08-20  2:11 ` [PATCH v16 2/7] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-08-20  2:11 ` [PATCH v16 3/7] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-08-27 22:02   ` Teres Alexis, Alan Previn
2024-08-27 22:27     ` Dong, Zhanjun
2024-08-20  2:11 ` [PATCH v16 4/7] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-08-20  2:11 ` [PATCH v16 5/7] drm/xe/guc: Move xe_lrc_snapshot to header file Zhanjun Dong
2024-08-27 20:40   ` Teres Alexis, Alan Previn
2024-08-20  2:11 ` Zhanjun Dong [this message]
2024-08-22  2:20   ` [PATCH v16 6/7] drm/xe/guc: Add dss conversion from group/instance ID Teres Alexis, Alan Previn
2024-08-20  2:11 ` [PATCH v16 7/7] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-08-20  2:17 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev16) Patchwork
2024-08-20  2:17 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-20  2:18 ` ✓ CI.KUnit: success " Patchwork
2024-08-20  2:30 ` ✓ CI.Build: " Patchwork
2024-08-20  2:32 ` ✓ CI.Hooks: " Patchwork
2024-08-20  2:34 ` ✓ CI.checksparse: " Patchwork
2024-08-20  2:57 ` ✗ CI.BAT: failure " Patchwork
2024-08-20 10:32 ` ✗ CI.FULL: " 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=20240820021142.436536-7-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