From: "Taylor, Clinton A" <clinton.a.taylor@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "Intel-xe@lists.freedesktop.org" <Intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Apply WA_14026810691 to engine
Date: Wed, 15 Apr 2026 20:18:01 +0000 [thread overview]
Message-ID: <8c0db43e18be50bc94b57ca339fdefb27bc0676c.camel@intel.com> (raw)
In-Reply-To: <20260415194726.GD755471@mdroper-desk1.amr.corp.intel.com>
On Wed, 2026-04-15 at 12:47 -0700, Matt Roper wrote:
> On Mon, Apr 13, 2026 at 01:08:25PM -0700, Clint Taylor wrote:
> > Apply engine tuning WA_14026810691 starting with IP: Xe3p_LPG
>
> The code changes look good, but I don't think we should refer to
> "WA_14026810691" in the subject and commit message for something that
> isn't actually a workaround and doesn't have an entry in the workaround
> database by that name. If you suggest an alternate wording, I can just
> make the changes while applying the patch; no need to re-submit and
> trigger another CI cycle.
>
New Title:
drm/xe/xe3p: add gt tuning TileY 2x2 walk pattern
-Clint
>
> Matt
>
> > v2: move to xe tunings (MattR)
> > Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
> > ---
> > drivers/gpu/drm/xe/regs/xe_gt_regs.h | 3 +++
> > drivers/gpu/drm/xe/xe_tuning.c | 5 +++++
> > 2 files changed, 8 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> > b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> > index aa267c2f6162..6a16ac1aca96 100644
> > --- a/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> > +++ b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> > @@ -536,6 +536,9 @@
> > #define SLM_WMTP_RESTORE REG_BIT(11)
> > #define RES_CHK_SPR_DIS REG_BIT(6)
> >
> > +#define TDL_TSL_CHICKEN2 XE_REG_MCR(0xe4cc, XE_REG_OPTION_MASKED)
> > +#define TILEY_LOCALID REG_BIT(2)
> > +
> > #define ROW_CHICKEN XE_REG_MCR(0xe4f0,
> > XE_REG_OPTION_MASKED)
> > #define UGM_BACKUP_MODE REG_BIT(13)
> > #define MDQ_ARBITRATION_MODE REG_BIT(12)
> > diff --git a/drivers/gpu/drm/xe/xe_tuning.c b/drivers/gpu/drm/xe/xe_tuning.c
> > index f8de6a4bf189..39423d5fabcc 100644
> > --- a/drivers/gpu/drm/xe/xe_tuning.c
> > +++ b/drivers/gpu/drm/xe/xe_tuning.c
> > @@ -124,6 +124,11 @@ static const struct xe_rtp_entry_sr engine_tunings[] = {
> > GHWSP_CSB_REPORT_DIS,
> > XE_RTP_ACTION_FLAG(ENGINE_BASE)))
> > },
> > + { XE_RTP_NAME("Tuning: TileY 2x2 Walk"),
> > + XE_RTP_RULES(GRAPHICS_VERSION_RANGE(3510, XE_RTP_END_VERSION_UNDEFINED),
> > + FUNC(xe_rtp_match_first_render_or_compute)),
> > + XE_RTP_ACTIONS(SET(TDL_TSL_CHICKEN2, TILEY_LOCALID))
> > + },
> > };
> >
> > static const struct xe_rtp_entry_sr lrc_tunings[] = {
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2026-04-15 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 20:08 [PATCH] drm/xe: Apply WA_14026810691 to engine Clint Taylor
2026-04-13 20:18 ` ✓ CI.KUnit: success for drm/xe: Apply WA_14026810691 to engine (rev2) Patchwork
2026-04-13 21:05 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-13 23:17 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-15 20:41 ` Matt Roper
2026-04-15 19:47 ` [PATCH] drm/xe: Apply WA_14026810691 to engine Matt Roper
2026-04-15 20:18 ` Taylor, Clinton A [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-09 21:57 Clint Taylor
2026-04-09 22:58 ` 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=8c0db43e18be50bc94b57ca339fdefb27bc0676c.camel@intel.com \
--to=clinton.a.taylor@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