Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "Shankar, Uma" <uma.shankar@intel.com>,
	"Joshi, Kunal1" <kunal1.joshi@intel.com>
Subject: Re: [PATCH] drm/i915/fbc: Apply wa_15018326506
Date: Fri, 7 Nov 2025 10:33:09 +0000	[thread overview]
Message-ID: <ea443f4c5bf41ff20f65bef1ee4e74313d76f62f.camel@intel.com> (raw)
In-Reply-To: <fb7031734a4c6b9cc0f26ff287fdf9fb23d07e65@intel.com>

On Fri, 2025-11-07 at 12:16 +0200, Jani Nikula wrote:
> On Fri, 07 Nov 2025, Vinod Govindapillai
> <vinod.govindapillai@intel.com> wrote:
> > Disable FBC as part for the wa for the bmg variant
> > 
> > Bspec: 74212
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_display_wa.c |  4 ++++
> >  drivers/gpu/drm/i915/display/intel_display_wa.h |  1 +
> >  drivers/gpu/drm/i915/display/intel_fbc.c        | 10 ++++++++++
> >  3 files changed, 15 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_wa.c
> > b/drivers/gpu/drm/i915/display/intel_display_wa.c
> > index c528aaa679ca..ba2272d85a04 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_wa.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display_wa.c
> > @@ -10,6 +10,7 @@
> >  #include "intel_display_core.h"
> >  #include "intel_display_regs.h"
> >  #include "intel_display_wa.h"
> > +#include "intel_step.h"
> >  
> >  static void gen11_display_wa_apply(struct intel_display *display)
> >  {
> > @@ -69,6 +70,9 @@ bool __intel_display_wa(struct intel_display
> > *display, enum intel_display_wa wa,
> >  		return DISPLAY_VER(display) == 13;
> >  	case INTEL_DISPLAY_WA_22014263786:
> >  		return IS_DISPLAY_VERx100(display, 1100, 1400);
> > +	case INTEL_DISPLAY_WA_15018326506:
> > +		return DISPLAY_VERx100(display) == 1401 &&
> > +		       INTEL_DISPLAY_STEP(display) == STEP_C0;
> 
> IS_DISPLAY_VERx100_STEP().

I was looking into the comments for that macro! This wa apply only for
step c0 (as of now)! I wasn't sure what the "until" part could be in
that macro! So what do you suggest for the "until"  STEP_D0 or
STEP_FOREVER in such cases!

BR
Vinod


> 
> >  	default:
> >  		drm_WARN(display->drm, 1, "Missing Wa number:
> > %s\n", name);
> >  		break;
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_wa.h
> > b/drivers/gpu/drm/i915/display/intel_display_wa.h
> > index 3644e8e2b724..f648b00cb97d 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_wa.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_wa.h
> > @@ -26,6 +26,7 @@ enum intel_display_wa {
> >  	INTEL_DISPLAY_WA_16025573575,
> >  	INTEL_DISPLAY_WA_14011503117,
> >  	INTEL_DISPLAY_WA_22014263786,
> > +	INTEL_DISPLAY_WA_15018326506,
> >  };
> >  
> >  bool __intel_display_wa(struct intel_display *display, enum
> > intel_display_wa wa, const char *name);
> > diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c
> > b/drivers/gpu/drm/i915/display/intel_fbc.c
> > index a1e3083022ee..16cd99db2978 100644
> > --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> > @@ -1521,6 +1521,16 @@ static int intel_fbc_check_plane(struct
> > intel_atomic_state *state,
> >  		return 0;
> >  	}
> >  
> > +	/*
> > +	 * wa_15018326506:
> > +	 * Fixes: Underrun during media decode
> > +	 * Workaround: Do not enable FBC
> > +	 */
> > +	if (intel_display_wa(display, 15018326506)) {
> > +		plane_state->no_fbc_reason = "Wa_15018326506";
> > +		return 0;
> > +	}
> > +
> >  	/* WaFbcTurnOffFbcWhenHyperVisorIsUsed:skl,bxt */
> >  	if (intel_display_vtd_active(display) &&
> >  	    (display->platform.skylake || display-
> > >platform.broxton)) {
> 


  reply	other threads:[~2025-11-07 10:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 10:07 [PATCH] drm/i915/fbc: Apply wa_15018326506 Vinod Govindapillai
2025-11-07 10:16 ` Jani Nikula
2025-11-07 10:33   ` Govindapillai, Vinod [this message]
2025-11-07 11:08     ` Jani Nikula
2025-11-07 13:45       ` Lucas De Marchi
2025-11-07 16:01         ` Govindapillai, Vinod
2025-11-07 16:19           ` Lucas De Marchi
2025-11-07 16:43             ` Matt Roper
2025-11-07 10:58 ` ✓ CI.KUnit: success for " Patchwork
2025-11-07 11:40 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-09  0:21 ` ✗ Xe.CI.Full: failure " 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=ea443f4c5bf41ff20f65bef1ee4e74313d76f62f.camel@intel.com \
    --to=vinod.govindapillai@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=kunal1.joshi@intel.com \
    --cc=uma.shankar@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