Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] i915: Extend Wa_1607297627 to Alderlake-P
Date: Mon, 17 Oct 2022 12:47:40 +0000	[thread overview]
Message-ID: <4dd3d7c9ae70b302fbd0b8e304db349e07d54ae2.camel@intel.com> (raw)
In-Reply-To: <44b8d200-8013-fcc2-3163-43f39b1bb5ec@linux.intel.com>

On Mon, 2022-10-17 at 09:51 +0100, Tvrtko Ursulin wrote:
> On 14/10/2022 23:08, Lucas De Marchi wrote:
> > On Thu, Oct 13, 2022 at 06:23:07PM +0000, Jose Souza wrote:
> > > missed the "drm/" in the subject 😛
> > 
> > with that,  Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
> 
> And where is the commit text? :p
> 
> Impact warrants fixes and/or cc stable 5.17+ for ADL-P force probe 
> removal or not?

Will add the fixes to adl-p force probe patch in the v2.

> 
> Regards,
> 
> Tvrtko
> 
> > 
> > Lucas De Marchi
> > 
> > > 
> > > On Thu, 2022-10-13 at 11:14 -0700, José Roberto de Souza wrote:
> > > > BSpec: 54369
> > > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > > ---
> > > >  drivers/gpu/drm/i915/gt/intel_workarounds.c | 4 ++--
> > > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > > 
> > > > diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c 
> > > > b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > > > index b8eb20a155f0d..e1d5df3a5756e 100644
> > > > --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > > > +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > > > @@ -2300,11 +2300,11 @@ rcs_engine_wa_init(struct intel_engine_cs 
> > > > *engine, struct i915_wa_list *wal)
> > > >      }
> > > > 
> > > >      if (IS_DG1_GRAPHICS_STEP(i915, STEP_A0, STEP_B0) ||
> > > > -        IS_ROCKETLAKE(i915) || IS_TIGERLAKE(i915)) {
> > > > +        IS_ROCKETLAKE(i915) || IS_TIGERLAKE(i915) || 
> > > > IS_ALDERLAKE_P(i915)) {
> > > >          /*
> > > >           * Wa_1607030317:tgl
> > > >           * Wa_1607186500:tgl
> > > > -         * Wa_1607297627:tgl,rkl,dg1[a0]
> > > > +         * Wa_1607297627:tgl,rkl,dg1[a0],adlp
> > > >           *
> > > >           * On TGL and RKL there are multiple entries for this WA in the
> > > >           * BSpec; some indicate this is an A0-only WA, others indicate
> > > 


  reply	other threads:[~2022-10-17 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 18:14 [Intel-gfx] [PATCH] i915: Extend Wa_1607297627 to Alderlake-P José Roberto de Souza
2022-10-13 18:23 ` Souza, Jose
2022-10-14 22:08   ` Lucas De Marchi
2022-10-17  8:51     ` Tvrtko Ursulin
2022-10-17 12:47       ` Souza, Jose [this message]
2022-10-13 20:03 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-10-13 21:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for i915: Extend Wa_1607297627 to Alderlake-P (rev2) Patchwork
2022-10-14  0:05 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=4dd3d7c9ae70b302fbd0b8e304db349e07d54ae2.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=tvrtko.ursulin@linux.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