Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	<intel-xe@lists.freedesktop.org>,
	 <intel-gfx@lists.freedesktop.org>
Cc: <matthew.d.roper@intel.com>
Subject: Re: [PATCH 2/3] drm/i915/psr: Change psr size limits check
Date: Mon, 28 Oct 2024 18:24:45 +0530	[thread overview]
Message-ID: <a1f6f1fc-4bbc-4172-974f-b0eba2752a21@intel.com> (raw)
In-Reply-To: <9bea7900-aa6a-4b2a-b82e-4e83bb7e728f@intel.com>


On 10/28/2024 6:14 PM, Nautiyal, Ankit K wrote:
>
> On 10/28/2024 1:13 PM, Suraj Kandpal wrote:
>> Change the check to only check for psr size limits till Pre-Xe2
>> since after that the psr size is equal to maximum pipe size anyways.
>>
>> --v2
>> -Check only size limit until pre-Xe2 [Matt]
>>
>> Bspec: 69885, 68858
>> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>
> LGTM.
>
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>
>> ---
>>   drivers/gpu/drm/i915/display/intel_psr.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c 
>> b/drivers/gpu/drm/i915/display/intel_psr.c
>> index 4176163ec19a..7bc64eae9c8e 100644
>> --- a/drivers/gpu/drm/i915/display/intel_psr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
>> @@ -1453,11 +1453,11 @@ static bool intel_psr2_config_valid(struct 
>> intel_dp *intel_dp,
>>           return false;
>>       }
>>   -    if (DISPLAY_VER(display) >= 12) {

I think you missed to initialize psr_max_{h,v} and max_bpp with 
crtc_{h,v}display and crtc_state->pipe_bpp respectively.

Otherwise those are all 0's and will fail for Display ver > 14.


Regards,

Ankit

>> +    if (IS_DISPLAY_VER(display, 12, 14)) {
>>           psr_max_h = 5120;
>>           psr_max_v = 3200;
>>           max_bpp = 30;
>> -    } else if (DISPLAY_VER(display) >= 10) {
>> +    } else if (IS_DISPLAY_VER(display, 10, 11)) {
>>           psr_max_h = 4096;
>>           psr_max_v = 2304;
>>           max_bpp = 24;

  reply	other threads:[~2024-10-28 12:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28  7:43 [PATCH 0/5] Add 6k resolution support for a single CRTC Suraj Kandpal
2024-10-28  7:43 ` [PATCH 1/3] drm/i915/xe3lpd: Increase resolution for plane to support 6k Suraj Kandpal
2024-10-28  7:43 ` [PATCH 2/3] drm/i915/psr: Change psr size limits check Suraj Kandpal
2024-10-28 12:44   ` Nautiyal, Ankit K
2024-10-28 12:54     ` Nautiyal, Ankit K [this message]
2024-10-28 13:00   ` Suraj Kandpal
2024-10-28 21:11   ` Matt Roper
2024-10-28  7:43 ` [PATCH 3/3] drm/i914/xe3lpd: Increase bigjoiner limitations Suraj Kandpal
2024-10-28 15:00 ` ✓ CI.Patch_applied: success for Add 6k resolution support for a single CRTC (rev5) Patchwork
2024-10-28 15:00 ` ✓ CI.checkpatch: " Patchwork
2024-10-28 15:02 ` ✓ CI.KUnit: " Patchwork
2024-10-28 15:20 ` ✓ CI.Build: " Patchwork
2024-10-28 15:23 ` ✓ CI.Hooks: " Patchwork
2024-10-28 15:24 ` ✗ CI.checksparse: warning " Patchwork
2024-10-28 16:09 ` ✓ CI.BAT: success " Patchwork
2024-10-28 17:19 ` ✗ CI.FULL: failure " Patchwork
2024-10-29 11:51 ` 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=a1f6f1fc-4bbc-4172-974f-b0eba2752a21@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --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