From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Syrjala, Ville" <ville.syrjala@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH 1/4] drm/i915/lnl: FBC can be enabled with PSR2
Date: Tue, 29 Aug 2023 12:16:33 +0000 [thread overview]
Message-ID: <62beb1e24bc20a22afd32385f0cd32d8a6e938de.camel@intel.com> (raw)
In-Reply-To: <20230828235801.GO6080@mdroper-desk1.amr.corp.intel.com>
On Mon, 2023-08-28 at 16:58 -0700, Matt Roper wrote:
> On Mon, Aug 28, 2023 at 09:20:32AM +0300, Vinod Govindapillai wrote:
> > FBC restriction with PSR2 can be removed from LNL onwards
> >
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_fbc.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> > index 66c8aed07bbc..d36499d7e0be 100644
> > --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> > @@ -1169,11 +1169,11 @@ static int intel_fbc_check_plane(struct intel_atomic_state *state,
> > }
> >
> > /*
> > - * Display 12+ is not supporting FBC with PSR2.
> > + * Display 12 to 14 is not supporting FBC with PSR2.
> > * Recommendation is to keep this combination disabled
> > * Bspec: 50422 HSD: 14010260002
> > */
> > - if (DISPLAY_VER(i915) >= 12 && crtc_state->has_psr2) {
> > + if (IS_DISPLAY_VER(i915, 12, 14) && crtc_state->has_psr2) {
>
> According to bspec 68881, the situation is more complicated than just
> flipping this back on. FBC + PSR2 should only be enabled together if a
> bunch of other conditions are met (multiple planes enabled, selective
> fetch is not enabled, etc.). Otherwise we may be hurting power usage
> rather than helping it by turning these two on together.
>
>
> Matt
Thanks for pointing this out! This patch was done based on the discussions VLK-50754
I can drop this patch for now and can reintroduce later with all the restrictions mentioned in 68881
if needed.
Thanks
Vinod
>
> > plane_state->no_fbc_reason = "PSR2 enabled";
> > return 0;
> > }
> > --
> > 2.34.1
> >
>
next prev parent reply other threads:[~2023-08-29 12:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 6:20 [Intel-xe] [PATCH 0/4] fbc on any plane Vinod Govindapillai
2023-08-28 6:20 ` [Intel-xe] [PATCH 1/4] drm/i915/lnl: FBC can be enabled with PSR2 Vinod Govindapillai
2023-08-28 23:58 ` Matt Roper
2023-08-29 12:16 ` Govindapillai, Vinod [this message]
2023-08-28 6:20 ` [Intel-xe] [PATCH 2/4] drm/i915/lnl: update FBC debugfs to include plane information Vinod Govindapillai
2023-08-29 0:01 ` Matt Roper
2023-08-29 7:46 ` Ville Syrjälä
2023-08-28 6:20 ` [Intel-xe] [PATCH 3/4] drm/i915/lnl: support FBC on any plane Vinod Govindapillai
2023-08-28 9:00 ` Jani Nikula
2023-08-28 10:10 ` Govindapillai, Vinod
2023-08-29 0:16 ` Matt Roper
2023-08-29 13:50 ` Govindapillai, Vinod
2023-08-29 16:04 ` Matt Roper
2023-08-30 6:06 ` [Intel-xe] [Intel-gfx] " Ville Syrjälä
2023-08-29 7:50 ` [Intel-xe] " Ville Syrjälä
2023-08-29 13:34 ` Govindapillai, Vinod
2023-08-30 5:34 ` Ville Syrjälä
2023-08-28 6:20 ` [Intel-xe] [PATCH 4/4] drm/i915/lnl: FBC is supported with per pixel alpha Vinod Govindapillai
2023-09-01 3:28 ` [Intel-xe] ✓ CI.Patch_applied: success for fbc on any plane (rev2) Patchwork
2023-09-01 3:28 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-01 3:29 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-01 3:36 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-01 3:36 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-01 3:37 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-01 4:09 ` [Intel-xe] ✓ CI.BAT: success " 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=62beb1e24bc20a22afd32385f0cd32d8a6e938de.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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