Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>,
	intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, ucas.demarchi@intel.com,
	kunal1.joshi@intel.com, jani.saarinen@intel.com
Subject: Re: [PATCH v2] drm/i915/fbc: update the impacted platforms in wa_22014263786
Date: Wed, 01 Oct 2025 13:03:03 +0300	[thread overview]
Message-ID: <09f6e8b565bfbecc38f5978bde824192924a1bc4@intel.com> (raw)
In-Reply-To: <20251001081209.272607-1-vinod.govindapillai@intel.com>

On Wed, 01 Oct 2025, Vinod Govindapillai <vinod.govindapillai@intel.com> wrote:
> wa_22014263786 is not applicable to the BMG and hence exclude it
> from the wa.
>
> v2: Limit this wa to display verion 11 to 14, drop DG2 from the
>     exclusion list, use intel_display_wa (Lucas)
>
> Bspec: 74212, 66624
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display_wa.c | 12 ++++++++++++
>  drivers/gpu/drm/i915/display/intel_display_wa.h |  1 +
>  drivers/gpu/drm/i915/display/intel_fbc.c        |  3 +--
>  3 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_wa.c b/drivers/gpu/drm/i915/display/intel_display_wa.c
> index 31cd2c9cd488..7ca238725e30 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_wa.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_wa.c
> @@ -52,6 +52,16 @@ static bool intel_display_needs_wa_16025573575(struct intel_display *display)
>  	return DISPLAY_VERx100(display) == 3000 || DISPLAY_VERx100(display) == 3002;
>  }
>  
> +/*
> + * Wa_22014263786:
> + * Fixes: Screen flicker with FBC and Package C state enabled
> + * Workaround: Forced SLB invalidation before start of new frame.
> + */
> +static bool intel_display_needs_wa_22014263786(struct intel_display *display)
> +{
> +	return DISPLAY_VERx100(display) >= 1100 && DISPLAY_VERx100(display) < 1401;

IS_DISPLAY_VERx100(display, 1100, 1400)

Also I'm not sure if we really need separate functions for one-liners
like this. The documentation could be in the switch case too? *shrug*.

BR,
Jani.

> +}
> +
>  /*
>   * Wa_14011503117:
>   * Fixes: Before enabling the scaler DE fatal error is masked
> @@ -67,6 +77,8 @@ bool __intel_display_wa(struct intel_display *display, enum intel_display_wa wa,
>  		return intel_display_needs_wa_16025573575(display);
>  	case INTEL_DISPLAY_WA_14011503117:
>  		return DISPLAY_VER(display) == 13;
> +	case INTEL_DISPLAY_WA_22014263786:
> +		return intel_display_needs_wa_22014263786(display);
>  	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 abc1df83f066..3644e8e2b724 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_wa.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_wa.h
> @@ -25,6 +25,7 @@ enum intel_display_wa {
>  	INTEL_DISPLAY_WA_16023588340,
>  	INTEL_DISPLAY_WA_16025573575,
>  	INTEL_DISPLAY_WA_14011503117,
> +	INTEL_DISPLAY_WA_22014263786,
>  };
>  
>  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 0d380c825791..9607fdcb0cc0 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> @@ -933,8 +933,7 @@ static void intel_fbc_program_workarounds(struct intel_fbc *fbc)
>  		intel_de_rmw(display, ILK_DPFC_CHICKEN(fbc->id),
>  			     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 (intel_display_wa(display, 22014263786))
>  		intel_de_rmw(display, ILK_DPFC_CHICKEN(fbc->id),
>  			     0, DPFC_CHICKEN_FORCE_SLB_INVALIDATION);

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-10-01 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  8:12 [PATCH v2] drm/i915/fbc: update the impacted platforms in wa_22014263786 Vinod Govindapillai
2025-10-01 10:03 ` Jani Nikula [this message]
2025-10-01 12:37   ` Govindapillai, Vinod
2025-10-01 13:10     ` Jani Nikula
2025-10-01 13:20       ` Govindapillai, Vinod
2025-10-01 17:19         ` Ville Syrjälä
2025-10-01 17:26           ` Ville Syrjälä
2025-10-01 10:24 ` ✗ i915.CI.BAT: failure for drm/i915/fbc: update the impacted platforms in wa_22014263786 (rev2) 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=09f6e8b565bfbecc38f5978bde824192924a1bc4@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=kunal1.joshi@intel.com \
    --cc=ucas.demarchi@intel.com \
    --cc=vinod.govindapillai@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