Intel-GFX 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: "Saarinen, Jani" <jani.saarinen@intel.com>,
	"Syrjala, Ville" <ville.syrjala@intel.com>
Subject: Re: [RFC PATCH 4/4] drm/i915/xe3: disable FBC if PSR2 selective fetch is enabled
Date: Tue, 19 Nov 2024 08:58:57 +0000	[thread overview]
Message-ID: <fa75e770bbfbdd679f07a0eb36986175252cf80a.camel@intel.com> (raw)
In-Reply-To: <87ttc338t3.fsf@intel.com>

On Tue, 2024-11-19 at 10:51 +0200, Jani Nikula wrote:
> On Tue, 19 Nov 2024, Vinod Govindapillai <vinod.govindapillai@intel.com> wrote:
> > FBC dirty rect support and PSR2 selective fetch canno be enabled
> > together. In xe3 driver enables the FBC dirty rect feature by
> > default. So PSR2 is enabled, then mark that plane as FBC cannot
> > be enabled. Later on we need to find a way to select between
> > FBC and PSR2 based on amount of damaged areas.
> > 
> > Bspec: 68881
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_fbc.c | 9 +++++++--
> >  1 file changed, 7 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> > index 01080171790f..e1d55f5f2938 100644
> > --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> > @@ -1346,9 +1346,14 @@ static int intel_fbc_check_plane(struct intel_atomic_state *state,
> >          * Display 12+ is not supporting FBC with PSR2.
> >          * 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
> >          */
> > -       if (IS_DISPLAY_VER(display, 12, 14) && crtc_state->has_sel_update &&
> > -           !crtc_state->has_panel_replay) {
> > +       if (IS_DISPLAY_VER(display, 12, 14) && DISPLAY_VER(display) >= 30 &&
> 
> This will never be true.
> 
> BR,
> Jani.

oops! Thanks! Will fix that!

BR
vinod
> 
> > +           crtc_state->has_sel_update && !crtc_state->has_panel_replay) {
> >                 plane_state->no_fbc_reason = "PSR2 enabled";
> >                 return 0;
> >         }
> 


  reply	other threads:[~2024-11-19  8:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 23:53 [RFC PATCH 0/4] drm/i915/xe3: FBC Dirty rect feature support Vinod Govindapillai
2024-11-18 23:53 ` [RFC PATCH 1/4] drm/i915/display: update intel_fbc_atomic_check for dirty_fbc support Vinod Govindapillai
2024-11-18 23:53 ` [RFC PATCH 2/4] drm/i915/display: add register definitions for fbc dirty rect support Vinod Govindapillai
2024-11-18 23:53 ` [RFC PATCH 3/4] drm/i915/xe3: add dirty rect support for FBC Vinod Govindapillai
2024-11-19  8:50   ` Jani Nikula
2024-11-22  8:31   ` Ville Syrjälä
2024-11-18 23:53 ` [RFC PATCH 4/4] drm/i915/xe3: disable FBC if PSR2 selective fetch is enabled Vinod Govindapillai
2024-11-19  8:51   ` Jani Nikula
2024-11-19  8:58     ` Govindapillai, Vinod [this message]
2024-11-19  0:37 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/xe3: FBC Dirty rect feature support Patchwork
2024-11-19  0:37 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-19  0:51 ` ✗ Fi.CI.BAT: 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=fa75e770bbfbdd679f07a0eb36986175252cf80a.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=jani.saarinen@intel.com \
    --cc=ville.syrjala@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