From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH 3/3] drm/xe: Mark ROW_CHICKEN5 as a masked register
Date: Mon, 13 Apr 2026 12:44:58 -0300 [thread overview]
Message-ID: <87h5peooed.fsf@intel.com> (raw)
In-Reply-To: <20260410-xe3p_tuning-v1-3-e206a62ee38f@intel.com>
Matt Roper <matthew.d.roper@intel.com> writes:
> ROW_CHICKEN5 is a masked register (i.e., to adjust the value of any of
> the lower 16 bits, the corresponding bit in the upper 16 bits must also
> be set). Add the XE_REG_OPTION_MASKED to its definition; failure to do
> so will cause workaround updates of this register to not apply properly.
>
> Bspec: 56853
> Fixes: 835cd6cbb0d0 ("drm/xe/xe3p_lpg: Add initial workarounds for graphics version 35.10")
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
It appears there was a Bspec update that accidentally dropped the
mask bits from the register description and then later on those were
added back (although the "masked" access tag remained). Maybe it is
likely that we were in between those those changes when this programming
was added to the driver?
--
Gustavo Sousa
> ---
> drivers/gpu/drm/xe/regs/xe_gt_regs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/regs/xe_gt_regs.h b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> index aa267c2f6162..a4472b7acb18 100644
> --- a/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> +++ b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> @@ -584,7 +584,7 @@
> #define DISABLE_128B_EVICTION_COMMAND_UDW REG_BIT(36 - 32)
> #define LSCFE_SAME_ADDRESS_ATOMICS_COALESCING_DISABLE REG_BIT(35 - 32)
>
> -#define ROW_CHICKEN5 XE_REG_MCR(0xe7f0)
> +#define ROW_CHICKEN5 XE_REG_MCR(0xe7f0, XE_REG_OPTION_MASKED)
> #define CPSS_AWARE_DIS REG_BIT(3)
>
> #define SARB_CHICKEN1 XE_REG_MCR(0xe90c)
>
> --
> 2.53.0
next prev parent reply other threads:[~2026-04-13 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 22:50 [PATCH 0/3] Xe3p tuning and workaround fixes Matt Roper
2026-04-10 22:50 ` [PATCH 1/3] drm/xe/tuning: Stop applying CCCHKNREG1 tuning from Xe3p onward Matt Roper
2026-04-13 15:28 ` Gustavo Sousa
2026-04-10 22:50 ` [PATCH 2/3] drm/xe/tuning: Use proper register offset for GAMSTLB_CTRL Matt Roper
2026-04-13 15:36 ` Gustavo Sousa
2026-04-13 19:17 ` Matt Roper
2026-04-13 20:50 ` Gustavo Sousa
2026-04-10 22:50 ` [PATCH 3/3] drm/xe: Mark ROW_CHICKEN5 as a masked register Matt Roper
2026-04-13 15:44 ` Gustavo Sousa [this message]
2026-04-10 23:35 ` ✓ CI.KUnit: success for Xe3p tuning and workaround fixes Patchwork
2026-04-11 0:17 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-11 10:51 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-13 19:42 ` Matt Roper
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=87h5peooed.fsf@intel.com \
--to=gustavo.sousa@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