Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Govindapillai, Vinod" <vinod.govindapillai@intel.com>
Cc: "Shankar, Uma" <uma.shankar@intel.com>,
	"Saarinen, Jani" <jani.saarinen@intel.com>,
	"Syrjala, Ville" <ville.syrjala@intel.com>,
	"B, Jeevan" <jeevan.b@intel.com>
Subject: Re: [PATCH v2 2/2] drm/i915/fbc: remove panel_replay dependency from fbc wa checks
Date: Thu, 20 Mar 2025 10:12:25 +0000	[thread overview]
Message-ID: <9db3c1ce3b61447085248c9dd444dde49a44cfef.camel@intel.com> (raw)
In-Reply-To: <20250319135130.122703-3-vinod.govindapillai@intel.com>

On Wed, 2025-03-19 at 15:51 +0200, Vinod Govindapillai wrote:
> Panel replay is supported from display 14 onwards. So no need
> to check the panel replay status in the previous gen workarounds.
> In the newer panel replay, selective update is supported and it
> is suffice to check selective update status for the workarounds
> in FBC use cases.
> 
> Bspec: 66624, 50442
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_fbc.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c
> b/drivers/gpu/drm/i915/display/intel_fbc.c
> index 92b00da4c0ab..2dc8ff734b11 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> @@ -1471,8 +1471,7 @@ static int intel_fbc_check_plane(struct
> intel_atomic_state *state,
>  	 * disabling PSR2, keep FBC disabled in case of selective
> update is on
>  	 * until the selection logic is implemented.
>  	 */
> -	if (DISPLAY_VER(display) >= 12 && crtc_state->has_sel_update
> &&
> -	    !crtc_state->has_panel_replay) {
> +	if (DISPLAY_VER(display) >= 12 && crtc_state-
> >has_sel_update) {
>  		plane_state->no_fbc_reason = "PSR2 enabled";

Probably you are sending update anyways so I think you could update
no_fbc_reason. E.g. Selective fetch/update enabled?

>  		return 0;
>  	}
> @@ -1480,7 +1479,7 @@ static int intel_fbc_check_plane(struct
> intel_atomic_state *state,
>  	/* Wa_14016291713 */
>  	if ((IS_DISPLAY_VER(display, 12, 13) ||
>  	     IS_DISPLAY_VERx100_STEP(display, 1400, STEP_A0,
> STEP_C0)) &&
> -	    crtc_state->has_psr && !crtc_state->has_panel_replay) {
> +	    crtc_state->has_psr) {

I don't think this is needed for Panel Replay.

BR,

Jouni Högander

>  		plane_state->no_fbc_reason = "PSR1 enabled
> (Wa_14016291713)";
>  		return 0;
>  	}


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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 13:51 [PATCH v2 0/2] update to FBC, PSR combo handling in xe2lpd Vinod Govindapillai
2025-03-19 13:51 ` [PATCH v2 1/2] drm/i915/fbc: keep FBC disabled if selective update is on " Vinod Govindapillai
2025-03-19 13:51 ` [PATCH v2 2/2] drm/i915/fbc: remove panel_replay dependency from fbc wa checks Vinod Govindapillai
2025-03-20 10:12   ` Hogander, Jouni [this message]
2025-03-20 10:42     ` Govindapillai, Vinod
2025-03-19 13:56 ` ✓ CI.Patch_applied: success for update to FBC, PSR combo handling in xe2lpd Patchwork
2025-03-19 13:56 ` ✓ CI.checkpatch: " Patchwork
2025-03-19 13:57 ` ✓ CI.KUnit: " Patchwork
2025-03-19 14:13 ` ✓ CI.Build: " Patchwork
2025-03-19 14:16 ` ✓ CI.Hooks: " Patchwork
2025-03-19 14:17 ` ✓ CI.checksparse: " Patchwork
2025-03-19 14:38 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-19 15:38 ` ✗ 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=9db3c1ce3b61447085248c9dd444dde49a44cfef.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=jeevan.b@intel.com \
    --cc=uma.shankar@intel.com \
    --cc=ville.syrjala@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