From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Garg, Nemesa" <nemesa.garg@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Saarinen, Jani" <jani.saarinen@intel.com>,
"Joshi, Kunal1" <kunal1.joshi@intel.com>,
"Hogander, Jouni" <jouni.hogander@intel.com>
Subject: Re: [PATCH] drm/i915/fbc: update the impacted platforms in wa_22014263786
Date: Thu, 25 Sep 2025 16:32:02 +0000 [thread overview]
Message-ID: <471fef17c747ee7b5998bfee9ea77ded05f73f2e.camel@intel.com> (raw)
In-Reply-To: <IA1PR11MB6467D2916BEDAC41E9993181E31FA@IA1PR11MB6467.namprd11.prod.outlook.com>
On Thu, 2025-09-25 at 13:15 +0000, Garg, Nemesa wrote:
>
>
> > -----Original Message-----
> > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Vinod
> > Govindapillai
> > Sent: Wednesday, September 24, 2025 3:33 PM
> > To: intel-xe@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
> > Cc: Govindapillai, Vinod <vinod.govindapillai@intel.com>; Hogander, Jouni
> > <jouni.hogander@intel.com>; Joshi, Kunal1 <kunal1.joshi@intel.com>;
> > Saarinen, Jani <jani.saarinen@intel.com>
> > Subject: [PATCH] drm/i915/fbc: update the impacted platforms in
> > wa_22014263786
> >
> > wa_22014263786 is not applicable to the BMG and hence exclude it from the
> > wa.
> >
> > Bspec: 74212, 66624
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_fbc.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c
> > b/drivers/gpu/drm/i915/display/intel_fbc.c
> > index 0d380c825791..2938ee4b64d8 100644
> > --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> > @@ -934,7 +934,8 @@ static void intel_fbc_program_workarounds(struct
> > intel_fbc *fbc)
> > 0, DPFC_CHICKEN_COMP_DUMMY_PIXEL);
> >
> > /* Wa_22014263786:icl,jsl,tgl,dg1,rkl,adls,adlp,mtl */
> > - if (DISPLAY_VER(display) >= 11 && !display->platform.dg2)
> > + if (DISPLAY_VER(display) >= 11 && !display->platform.dg2 &&
> > + !display->platform.battlemage)
> > intel_de_rmw(display, ILK_DPFC_CHICKEN(fbc->id),
> > 0, DPFC_CHICKEN_FORCE_SLB_INVALIDATION);
> >
> From wa it seems that it is limited to display 14.
Yes! I misinterpreted the "Project" column in bspec 66624! will update the patch!
Vinod
>
> Thanks and Regards,
> Nemesa
> > --
> > 2.43.0
>
prev parent reply other threads:[~2025-09-25 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 10:03 [PATCH] drm/i915/fbc: update the impacted platforms in wa_22014263786 Vinod Govindapillai
2025-09-24 10:10 ` ✓ CI.KUnit: success for " Patchwork
2025-09-24 10:48 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-24 10:55 ` ✓ i915.CI.BAT: " Patchwork
2025-09-24 13:16 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-24 19:41 ` ✓ i915.CI.Full: success " Patchwork
2025-09-24 20:46 ` [PATCH] " Lucas De Marchi
2025-09-25 16:31 ` Govindapillai, Vinod
2025-09-25 16:40 ` Lucas De Marchi
2025-09-25 13:15 ` Garg, Nemesa
2025-09-25 16:32 ` Govindapillai, Vinod [this message]
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=471fef17c747ee7b5998bfee9ea77ded05f73f2e.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=jouni.hogander@intel.com \
--cc=kunal1.joshi@intel.com \
--cc=nemesa.garg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.