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 1/2] drm/i915/fbc: keep FBC disabled if selective update is on in xe2lpd
Date: Fri, 21 Mar 2025 13:14:48 +0000 [thread overview]
Message-ID: <f52fae5f3b52d5f6c2d55af9ea4f84d6ea00b3f3.camel@intel.com> (raw)
In-Reply-To: <20250321094529.197397-2-vinod.govindapillai@intel.com>
On Fri, 2025-03-21 at 11:45 +0200, Vinod Govindapillai wrote:
> FBC was disabled in case PSR2 selective update in display 12 to
> 14 as part of a wa. From xe2lpd onwards there is a logic to be
> implemented to decide between FBC and selective update. Until
> that logic is implemented keep FBC disabled in case selective
> update is enabled.
>
> v1: updated patch description and some explanation and todo
>
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_fbc.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c
> b/drivers/gpu/drm/i915/display/intel_fbc.c
> index b6978135e8ad..92b00da4c0ab 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> @@ -1464,13 +1464,15 @@ static int intel_fbc_check_plane(struct
> intel_atomic_state *state,
> * Recommendation is to keep this combination disabled
> * Bspec: 50422 HSD: 14010260002
> *
> - * In Xe3, PSR2 selective fetch and FBC dirty rect feature
> cannot
> - * coexist. So if PSR2 selective fetch is supported then
> mark that
> - * FBC is not supported.
> - * TODO: Need a logic to decide between PSR2 and FBC Dirty
> rect
> + * TODO: Implement a logic to select between PSR2 selective
> fetch and
> + * FBC based on Bspec: 68881 in xe2lpd onwards.
> + *
> + * As we still see some strange underruns in those platforms
> while
> + * disabling PSR2, keep FBC disabled in case of selective
> update is on
> + * until the selection logic is implemented.
> */
> - if ((IS_DISPLAY_VER(display, 12, 14) ||
> HAS_FBC_DIRTY_RECT(display)) &&
> - crtc_state->has_sel_update && !crtc_state-
> >has_panel_replay) {
> + if (DISPLAY_VER(display) >= 12 && crtc_state->has_sel_update
> &&
> + !crtc_state->has_panel_replay) {
> plane_state->no_fbc_reason = "PSR2 enabled";
> return 0;
> }
next prev parent reply other threads:[~2025-03-21 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 9:45 [PATCH v2 0/2] drm/i915/fbc: disable FBC if PSR2 selective fetch is enabled Vinod Govindapillai
2025-03-21 9:45 ` [PATCH v2 1/2] drm/i915/fbc: keep FBC disabled if selective update is on in xe2lpd Vinod Govindapillai
2025-03-21 13:14 ` Hogander, Jouni [this message]
2025-03-25 3:40 ` B, Jeevan
2025-03-21 9:45 ` [PATCH v2 2/2] drm/i915/fbc: update the panel_replay dependency in fbc wa's Vinod Govindapillai
2025-03-21 13:15 ` Hogander, Jouni
2025-03-21 9:50 ` ✓ CI.Patch_applied: success for drm/i915/fbc: disable FBC if PSR2 selective fetch is enabled (rev3) Patchwork
2025-03-21 9:50 ` ✓ CI.checkpatch: " Patchwork
2025-03-21 9:51 ` ✓ CI.KUnit: " Patchwork
2025-03-21 10:16 ` ✓ CI.Build: " Patchwork
2025-03-21 10:20 ` ✓ CI.Hooks: " Patchwork
2025-03-21 10:22 ` ✓ CI.checksparse: " Patchwork
2025-03-21 10:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-21 11:59 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
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
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=f52fae5f3b52d5f6c2d55af9ea4f84d6ea00b3f3.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