From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: Violet Monti <violet.monti@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH 1/4] drm/xe: Reformat xe_rtp_types.h
Date: Tue, 16 Jun 2026 19:09:30 -0300 [thread overview]
Message-ID: <874ij2uoh1.fsf@intel.com> (raw)
In-Reply-To: <20260616-rtp_with_dynamic_vals-v1-1-f2b47bea9dd3@intel.com>
Matt Roper <matthew.d.roper@intel.com> writes:
> Adjust whitespace / newlines in xe_rtp_types.h to make it easier to read
> and more consistent with other files. No functional change.
>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
> ---
> drivers/gpu/drm/xe/xe_rtp_types.h | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_rtp_types.h b/drivers/gpu/drm/xe/xe_rtp_types.h
> index 58018ae4f8cc..1d7c63d0ae94 100644
> --- a/drivers/gpu/drm/xe/xe_rtp_types.h
> +++ b/drivers/gpu/drm/xe/xe_rtp_types.h
> @@ -22,20 +22,24 @@ struct xe_gt;
> */
> struct xe_rtp_action {
> /** @reg: Register */
> - struct xe_reg reg;
> + struct xe_reg reg;
> +
> /**
> * @clr_bits: bits to clear when updating register. It's always a
> * superset of bits being modified
> */
> - u32 clr_bits;
> + u32 clr_bits;
> +
> /** @set_bits: bits to set when updating register */
> - u32 set_bits;
> + u32 set_bits;
> +
> #define XE_RTP_NOCHECK .read_mask = 0
> /** @read_mask: mask for bits to consider when reading value back */
> - u32 read_mask;
> + u32 read_mask;
> +
> #define XE_RTP_ACTION_FLAG_ENGINE_BASE BIT(0)
> /** @flags: flags to apply on rule evaluation or action */
> - u8 flags;
> + u8 flags;
> };
>
> enum {
> @@ -69,6 +73,7 @@ struct xe_rtp_rule {
> u8 platform;
> u8 subplatform;
> };
> +
> /*
> * MATCH_GRAPHICS_VERSION / XE_RTP_MATCH_GRAPHICS_VERSION_RANGE /
> * MATCH_MEDIA_VERSION / XE_RTP_MATCH_MEDIA_VERSION_RANGE
> @@ -78,15 +83,18 @@ struct xe_rtp_rule {
> #define XE_RTP_END_VERSION_UNDEFINED U32_MAX
> u32 ver_end;
> };
> +
> /* MATCH_STEP */
> struct {
> u8 step_start;
> u8 step_end;
> };
> +
> /* MATCH_ENGINE_CLASS / MATCH_NOT_ENGINE_CLASS */
> struct {
> u8 engine_class;
> };
> +
> /* MATCH_FUNC */
> bool (*match_func)(const struct xe_device *xe,
> const struct xe_gt *gt,
>
> --
> 2.54.0
next prev parent reply other threads:[~2026-06-16 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 19:21 [PATCH 0/4] Move RTP tables for engine init off the stack Matt Roper
2026-06-16 19:21 ` [PATCH 1/4] drm/xe: Reformat xe_rtp_types.h Matt Roper
2026-06-16 22:09 ` Gustavo Sousa [this message]
2026-06-16 19:21 ` [PATCH 2/4] drm/xe/rtp: Add FIELD_SET_FUNC RTP action Matt Roper
2026-06-16 22:22 ` Gustavo Sousa
2026-06-16 19:21 ` [PATCH 3/4] drm/xe: Move engines' LRC programming RTP table off the stack Matt Roper
2026-06-16 19:54 ` Matt Roper
2026-06-16 22:26 ` Gustavo Sousa
2026-06-16 19:21 ` [PATCH 4/4] drm/xe: Move engines' non-LRC " Matt Roper
2026-06-16 22:33 ` Gustavo Sousa
2026-06-16 19:28 ` ✗ CI.checkpatch: warning for Move RTP tables for engine init " Patchwork
2026-06-16 19:29 ` ✓ CI.KUnit: success " Patchwork
2026-06-16 20:19 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-17 0:31 ` ✓ Xe.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=874ij2uoh1.fsf@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=violet.monti@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