From: Matt Roper <matthew.d.roper@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <lucas.demarchi@intel.com>,
<rodrigo.vivi@intel.com>
Subject: Re: [PATCH 04/10] drm/xe/step: define more steppings E-J
Date: Tue, 20 Aug 2024 15:48:14 -0700 [thread overview]
Message-ID: <20240820224814.GP5091@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <88074394509d4849f8ec6ab5776394b961032cd0.1724180287.git.jani.nikula@intel.com>
On Tue, Aug 20, 2024 at 10:00:37PM +0300, Jani Nikula wrote:
> These are primarily needed for compat reasons with display code in
> upcoming changes. There's no harm in having them.
>
> While at it, add a comment about the requirement to match against GMD ID
> value spacing.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/xe/xe_step_types.h | 29 ++++++++++++++++++++++++++++-
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_step_types.h b/drivers/gpu/drm/xe/xe_step_types.h
> index ccc9b4795e95..95b38d2d6c50 100644
> --- a/drivers/gpu/drm/xe/xe_step_types.h
> +++ b/drivers/gpu/drm/xe/xe_step_types.h
> @@ -17,6 +17,10 @@ struct xe_step_info {
>
> #define STEP_ENUM_VAL(name) STEP_##name,
>
> +/*
> + * Always define four minor steppings 0-3 for each stepping to match GMD ID
> + * spacing of values. See xe_step_gmdid_get().
> + */
> #define STEP_NAME_LIST(func) \
> func(A0) \
> func(A1) \
> @@ -34,7 +38,30 @@ struct xe_step_info {
> func(D1) \
> func(D2) \
> func(D3) \
> - func(E0)
> + func(E0) \
> + func(E1) \
> + func(E2) \
> + func(E3) \
> + func(F0) \
> + func(F1) \
> + func(F2) \
> + func(F3) \
> + func(G0) \
> + func(G1) \
> + func(G2) \
> + func(G3) \
> + func(H0) \
> + func(H1) \
> + func(H2) \
> + func(H3) \
> + func(I0) \
> + func(I1) \
> + func(I2) \
> + func(I3) \
> + func(J0) \
> + func(J1) \
> + func(J2) \
> + func(J3)
>
> /*
> * Symbolic steppings that do not match the hardware. These are valid both as gt
> --
> 2.39.2
>
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2024-08-20 22:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 19:00 [PATCH 00/10] drm/i915/display: identify display steppings in display code Jani Nikula
2024-08-20 19:00 ` [PATCH 01/10] drm/xe/display: fix compat IS_DISPLAY_STEP() range end Jani Nikula
2024-08-20 19:31 ` Lucas De Marchi
2024-08-20 22:29 ` Matt Roper
2024-08-20 19:00 ` [PATCH 02/10] drm/xe/display: remove intel_display_step_name() to simplify Jani Nikula
2024-08-20 22:32 ` Matt Roper
2024-08-20 19:00 ` [PATCH 03/10] drm/xe/display: remove the unused compat HAS_GMD_ID() Jani Nikula
2024-08-20 22:40 ` Matt Roper
2024-08-20 19:00 ` [PATCH 04/10] drm/xe/step: define more steppings E-J Jani Nikula
2024-08-20 22:48 ` Matt Roper [this message]
2024-08-20 19:00 ` [PATCH 05/10] drm/i915/display: rename IS_DISPLAY_IP_RANGE() to IS_DISPLAY_VER_FULL() Jani Nikula
2024-08-20 22:54 ` Matt Roper
2024-08-20 19:00 ` [PATCH 06/10] drm/i915/display: rename IS_DISPLAY_IP_STEP() to IS_DISPLAY_VER_STEP() Jani Nikula
2024-08-20 22:56 ` Matt Roper
2024-08-20 19:00 ` [PATCH 07/10] drm/i915/display: identify display steppings in display probe Jani Nikula
2024-08-20 23:52 ` Matt Roper
2024-08-21 8:59 ` Jani Nikula
2024-08-21 9:50 ` [PATCH v2] " Jani Nikula
2024-08-21 13:48 ` Matt Roper
2024-08-21 13:52 ` Gustavo Sousa
2024-08-21 14:30 ` Jani Nikula
2024-08-20 19:00 ` [PATCH 08/10] drm/i915/display: switch to display detected steppings Jani Nikula
2024-08-21 0:01 ` Matt Roper
2024-08-20 19:00 ` [PATCH 09/10] drm/i915: remove display stepping handling Jani Nikula
2024-08-21 0:04 ` Matt Roper
2024-08-21 0:08 ` Matt Roper
2024-08-20 19:00 ` [PATCH 10/10] drm/xe: " Jani Nikula
2024-08-21 0:04 ` Matt Roper
2024-08-20 19:51 ` ✓ CI.Patch_applied: success for drm/i915/display: identify display steppings in display code Patchwork
2024-08-20 19:51 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-20 19:52 ` ✓ CI.KUnit: success " Patchwork
2024-08-20 20:04 ` ✓ CI.Build: " Patchwork
2024-08-20 20:06 ` ✓ CI.Hooks: " Patchwork
2024-08-20 20:08 ` ✗ CI.checksparse: warning " Patchwork
2024-08-20 20:31 ` ✗ CI.BAT: failure " Patchwork
2024-08-21 2:35 ` ✗ CI.FULL: " Patchwork
2024-08-21 9:55 ` ✓ CI.Patch_applied: success for drm/i915/display: identify display steppings in display code (rev2) Patchwork
2024-08-21 9:56 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-21 9:57 ` ✓ CI.KUnit: success " Patchwork
2024-08-21 10:09 ` ✓ CI.Build: " Patchwork
2024-08-21 10:11 ` ✓ CI.Hooks: " Patchwork
2024-08-21 10:12 ` ✗ CI.checksparse: warning " Patchwork
2024-08-21 10:33 ` ✓ CI.BAT: success " Patchwork
2024-08-21 11:41 ` ✗ CI.FULL: failure " Patchwork
2024-08-22 10:52 ` [PATCH 00/10] drm/i915/display: identify display steppings in display code Jani Nikula
2024-08-22 12:32 ` Lucas De Marchi
2024-08-22 13:29 ` Jani Nikula
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=20240820224814.GP5091@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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