From: Anusha Srivatsa <anusha.srivatsa@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: [Intel-xe] [PATCH 4/5] drm/xe/rpls: Add Stepping info for RPLS
Date: Tue, 3 Oct 2023 13:37:15 -0700 [thread overview]
Message-ID: <20231003203716.108979-5-anusha.srivatsa@intel.com> (raw)
In-Reply-To: <20231003203716.108979-1-anusha.srivatsa@intel.com>
Add stepping-substepping info. Though it looks
weird, the revision ID for the newer stepping
is indeed backwards and is in accordance to the spec.
v2: s/RPLS/RAPTORLAKE_S (Anusha)
v3: rebase (Anusha)
Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>(v1)
---
drivers/gpu/drm/xe/xe_step.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_step.c b/drivers/gpu/drm/xe/xe_step.c
index 903c65405d3a..eaf1b718f26c 100644
--- a/drivers/gpu/drm/xe/xe_step.c
+++ b/drivers/gpu/drm/xe/xe_step.c
@@ -60,6 +60,11 @@ static const struct xe_step_info adls_revids[] = {
[0xC] = { COMMON_GT_MEDIA_STEP(D0), .display = STEP_C0 },
};
+static const struct xe_step_info adls_rpls_revids[] = {
+ [0x4] = { COMMON_GT_MEDIA_STEP(D0), .display = STEP_D0 },
+ [0xC] = { COMMON_GT_MEDIA_STEP(D0), .display = STEP_C0 },
+};
+
static const struct xe_step_info adlp_revids[] = {
[0x0] = { COMMON_GT_MEDIA_STEP(A0), .display = STEP_A0 },
[0x4] = { COMMON_GT_MEDIA_STEP(B0), .display = STEP_B0 },
@@ -143,6 +148,9 @@ struct xe_step_info xe_step_pre_gmdid_get(struct xe_device *xe)
} else if (xe->info.platform == XE_ALDERLAKE_N) {
revids = adln_revids;
size = ARRAY_SIZE(adln_revids);
+ } else if (xe->info.subplatform == XE_SUBPLATFORM_ALDERLAKE_S_RPLS) {
+ revids = adls_rpls_revids;
+ size = ARRAY_SIZE(adls_rpls_revids);
} else if (xe->info.subplatform == XE_SUBPLATFORM_ALDERLAKE_P_RPLU) {
revids = adlp_rpl_revids;
size = ARRAY_SIZE(adlp_rpl_revids);
--
2.25.1
next prev parent reply other threads:[~2023-10-03 20:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 20:37 [Intel-xe] [PATCH 0/5] Add Raptorlake Support Anusha Srivatsa
2023-10-03 20:37 ` [Intel-xe] [PATCH 1/5] drm/xe/rplu: s/ADLP/ALDERLAKE_P Anusha Srivatsa
2023-10-04 18:12 ` Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 2/5] fixup! " Anusha Srivatsa
2023-10-04 7:58 ` Jani Nikula
2023-10-04 18:16 ` Lucas De Marchi
2023-10-05 18:41 ` Rodrigo Vivi
2023-10-06 7:39 ` Jani Nikula
2023-10-03 20:37 ` [Intel-xe] [PATCH 3/5] drm/xe/rpls: Add RPLS Support Anusha Srivatsa
2023-10-04 18:19 ` Lucas De Marchi
2023-10-03 20:37 ` Anusha Srivatsa [this message]
2023-10-04 18:20 ` [Intel-xe] [PATCH 4/5] drm/xe/rpls: Add Stepping info for RPLS Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 5/5] drm/xe: Add missing ADL entries to xe_test_wa Anusha Srivatsa
2023-10-04 18:20 ` Lucas De Marchi
2023-10-03 22:04 ` [Intel-xe] ✓ CI.Patch_applied: success for Add Raptorlake Support (rev3) Patchwork
2023-10-03 22:04 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-10-03 22:06 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-10-03 22:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-03 22:13 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-03 22:14 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-10-03 22:52 ` [Intel-xe] ✓ CI.BAT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-10-05 20:54 [Intel-xe] [PATCH 0/5] Add Raptorlake Support Anusha Srivatsa
2023-10-05 20:54 ` [Intel-xe] [PATCH 4/5] drm/xe/rpls: Add Stepping info for RPLS Anusha Srivatsa
2023-09-29 20:16 [Intel-xe] [PATCH 0/5] Add Raptorlake Support Anusha Srivatsa
2023-09-29 20:16 ` [Intel-xe] [PATCH 4/5] drm/xe/rpls: Add Stepping info for RPLS Anusha Srivatsa
2023-05-26 21:17 [Intel-xe] [PATCH 0/5] RPLS and other minor support Anusha Srivatsa
2023-05-26 21:17 ` [Intel-xe] [PATCH 4/5] drm/xe/rpls: Add Stepping info for RPLS Anusha Srivatsa
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=20231003203716.108979-5-anusha.srivatsa@intel.com \
--to=anusha.srivatsa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
/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