Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Atwood <matthew.s.atwood@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	<intel-xe@lists.freedesktop.org>,  <tejas.upadhyay@intel.com>,
	<lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/xe/xe3: Extend wa_15015404425 for xe3
Date: Thu, 6 Feb 2025 09:12:49 -0800	[thread overview]
Message-ID: <Z6Ttkcj_XWatYkkF@msatwood-mobl> (raw)
In-Reply-To: <20250130173030.GH4460@mdroper-desk1.amr.corp.intel.com>

On Thu, Jan 30, 2025 at 09:30:30AM -0800, Matt Roper wrote:
> On Tue, Jan 28, 2025 at 04:55:51PM -0800, Matt Atwood wrote:
> > From: Tejas Upadhyay <tejas.upadhyay@intel.com>
> > 
> > wa_15015404425 applies to xe3 A0 step as well.
> 
> We really need a better commit message explaining how this workaround is
> different from our usual ones and why it needs to be handled in a
> special way that's different from all of our other workarounds,
> especially since someone who just quickly skims the workaround database
> without digging into the details is going to incorrectly think this just
> applies to Xe2 media and isn't relevant to PTL.
Ack.
> 
> I was kind of hoping we'd add a more well-defined infrastructure for
> handling device / SoC workarounds.  Adding quick hacks like this is
> going to get out of hand quickly if more of these start showing up.
Any particular ideas here?
+Lucas
> 
> 
> Matt
> 
> > 
> > v2: query based off SOC stepping
> > 
> > Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
> > Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_mmio.c | 13 +++++++------
> >  drivers/gpu/drm/xe/xe_step.h |  2 ++
> >  2 files changed, 9 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_mmio.c b/drivers/gpu/drm/xe/xe_mmio.c
> > index d321a21aacf0..98d068ad33bb 100644
> > --- a/drivers/gpu/drm/xe/xe_mmio.c
> > +++ b/drivers/gpu/drm/xe/xe_mmio.c
> > @@ -150,14 +150,15 @@ int xe_mmio_init(struct xe_device *xe)
> >  static void mmio_flush_pending_writes(struct xe_mmio *mmio)
> >  {
> >  #define DUMMY_REG_OFFSET	0x130030
> > +	struct xe_device *xe = tile_to_xe(mmio->tile);
> >  	int i;
> >  
> > -	if (mmio->tile->xe->info.platform != XE_LUNARLAKE)
> > -		return;
> > -
> > -	/* 4 dummy writes */
> > -	for (i = 0; i < 4; i++)
> > -		writel(0, mmio->regs + DUMMY_REG_OFFSET);
> > +	if (xe->info.platform == XE_LUNARLAKE ||
> > +	    (xe->info.platform == XE_PANTHERLAKE &&
> > +	     xe->info.revid == PTL_SOC_STEP_A0))
> > +		/* 4 dummy writes */
> > +		for (i = 0; i < 4; i++)
> > +			writel(0, mmio->regs + DUMMY_REG_OFFSET);
> >  }
> >  
> >  u8 xe_mmio_read8(struct xe_mmio *mmio, struct xe_reg reg)
> > diff --git a/drivers/gpu/drm/xe/xe_step.h b/drivers/gpu/drm/xe/xe_step.h
> > index 686cb59200c2..879486a818e9 100644
> > --- a/drivers/gpu/drm/xe/xe_step.h
> > +++ b/drivers/gpu/drm/xe/xe_step.h
> > @@ -20,4 +20,6 @@ static inline u32 xe_step_to_gmdid(enum xe_step step) { return step - STEP_A0; }
> >  
> >  const char *xe_step_name(enum xe_step step);
> >  
> > +#define PTL_SOC_STEP_A0  0x0
> > +
> >  #endif
> > -- 
> > 2.45.0
> > 
> 
> -- 
> Matt Roper
> Graphics Software Engineer
> Linux GPU Platform Enablement
> Intel Corporation

  reply	other threads:[~2025-02-06 17:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29  0:55 [PATCH] drm/xe/xe3: Extend wa_15015404425 for xe3 Matt Atwood
2025-01-29  2:19 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-29  2:19 ` ✓ CI.checkpatch: " Patchwork
2025-01-29  2:21 ` ✓ CI.KUnit: " Patchwork
2025-01-29  2:37 ` ✓ CI.Build: " Patchwork
2025-01-29  2:39 ` ✗ CI.Hooks: failure " Patchwork
2025-01-29  2:41 ` ✓ CI.checksparse: success " Patchwork
2025-01-29  3:00 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-29 16:38 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-30 17:30 ` [PATCH] " Matt Roper
2025-02-06 17:12   ` Matt Atwood [this message]
2025-02-06 23:33     ` Lucas De Marchi
2025-02-07  4:56       ` Upadhyay, Tejas
2025-02-07 16:24         ` Matt Roper
2025-02-07 17:03           ` Matt Atwood

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=Z6Ttkcj_XWatYkkF@msatwood-mobl \
    --to=matthew.s.atwood@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=tejas.upadhyay@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