From: Matt Roper <matthew.d.roper@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>, <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH 3/5] drm/i915/psr: Increase psr size limits for Xe2
Date: Fri, 25 Oct 2024 15:01:23 -0700 [thread overview]
Message-ID: <20241025220123.GU5725@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20241025060136.9884-4-suraj.kandpal@intel.com>
On Fri, Oct 25, 2024 at 11:31:34AM +0530, Suraj Kandpal wrote:
> Increase the psr max_h limit to 4096.
Commit message doesn't match code (this should probably say max_v
instead of max_h).
Since PSR2 size is supported up to the maximum pipe size now (for both
Xe2 and Xe3) would it be simpler to just make the check on psr_max_{h,v}
conditional to pre-Xe2? Then if we don't have any truly PSR-specific
limits, we don't need to keep duplicating the pipe limits in two places
going forward.
Matt
>
> Bspec: 69885, 68858
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_psr.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index 4176163ec19a..c22386a31a63 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -1453,7 +1453,11 @@ static bool intel_psr2_config_valid(struct intel_dp *intel_dp,
> return false;
> }
>
> - if (DISPLAY_VER(display) >= 12) {
> + if (DISPLAY_VER(display) >= 20) {
> + psr_max_h = 5120;
> + psr_max_v = 4096;
> + max_bpp = 30;
> + } else if (DISPLAY_VER(display) >= 12) {
> psr_max_h = 5120;
> psr_max_v = 3200;
> max_bpp = 30;
> --
> 2.34.1
>
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2024-10-25 22:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 6:01 [PATCH 0/5] Add 6k resolution support for a single CRTC Suraj Kandpal
2024-10-25 6:01 ` [PATCH 1/5] drm/i915/display: Fix the plane max height and width limits Suraj Kandpal
2024-10-25 6:21 ` Ville Syrjälä
2024-10-25 6:26 ` Kandpal, Suraj
2024-10-25 7:15 ` Ville Syrjälä
2024-10-25 7:24 ` Nautiyal, Ankit K
2024-10-25 8:04 ` Ville Syrjälä
2024-10-28 4:13 ` Kandpal, Suraj
2024-10-25 6:01 ` [PATCH 2/5] drm/i915/xe3lpd: Increase resolution for plane to support 6k Suraj Kandpal
2024-10-25 6:01 ` [PATCH 3/5] drm/i915/psr: Increase psr size limits for Xe2 Suraj Kandpal
2024-10-25 22:01 ` Matt Roper [this message]
2024-10-28 3:51 ` Kandpal, Suraj
2024-10-28 7:22 ` Hogander, Jouni
2024-10-28 5:00 ` Kandpal, Suraj
2024-10-25 6:01 ` [PATCH 4/5] drm/i915/xe3lpd: Increase max_h max_v for PSR Suraj Kandpal
2024-10-25 6:01 ` [PATCH 5/5] drm/i914/xe3lpd: Increase bigjoiner limitations Suraj Kandpal
2024-10-25 6:07 ` ✓ CI.Patch_applied: success for Add 6k resolution support for a single CRTC (rev3) Patchwork
2024-10-25 6:08 ` ✓ CI.checkpatch: " Patchwork
2024-10-25 6:09 ` ✓ CI.KUnit: " Patchwork
2024-10-25 6:20 ` ✓ CI.Build: " Patchwork
2024-10-25 6:23 ` ✓ CI.Hooks: " Patchwork
2024-10-25 6:24 ` ✗ CI.checksparse: warning " Patchwork
2024-10-25 6:46 ` ✓ CI.BAT: success " Patchwork
2024-10-26 16:11 ` ✗ 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=20241025220123.GU5725@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@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