All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Grzelak, Michal" <michal.grzelak@intel.com>,
	"B, Jeevan" <jeevan.b@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: RE: [PATCH i-g-t v1 1/2] lib/igt_psr: Skip the test when PSR is disabled
Date: Wed, 04 Jun 2025 14:48:09 +0300	[thread overview]
Message-ID: <14806d021fac55a7145795dfd254ea3ad7171e4f@intel.com> (raw)
In-Reply-To: <SJ0PR11MB50721CC4FBE56C699B83FE5B8F62A@SJ0PR11MB5072.namprd11.prod.outlook.com>

On Mon, 02 Jun 2025, "Grzelak, Michal" <michal.grzelak@intel.com> wrote:
> Hi Jeevan,
>
>> -----Original Message-----
>> From: B, Jeevan <jeevan.b@intel.com> 
>> Sent: Monday, May 26, 2025 7:38 AM
>> To: Grzelak, Michal <michal.grzelak@intel.com>; igt-dev@lists.freedesktop.org
>> Cc: Grzelak, Michal <michal.grzelak@intel.com>
>> Subject: RE: [PATCH i-g-t v1 1/2] lib/igt_psr: Skip the test when PSR is disabled
>
>>> -----Original Message-----
>>> From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of 
>>> Michal Grzelak
>>> Sent: Tuesday, May 13, 2025 5:49 PM
>>> To: igt-dev@lists.freedesktop.org
>>> Cc: Grzelak, Michal <michal.grzelak@intel.com>
>>> Subject: [PATCH i-g-t v1 1/2] lib/igt_psr: Skip the test when PSR is 
>>> disabled
>>> 
>>> If PSR setup timing is not met, then PSR will stay disabled and test 
>>> will fail anyway. Skip the test upon finding that setup timing was not met.
>>> 
>>> Signed-off-by: Michał Grzelak <michal.grzelak@intel.com>
>>> ---
>>>  lib/igt_psr.c | 4 +++-
>>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>> 
>>> diff --git a/lib/igt_psr.c b/lib/igt_psr.c index 3d8f1949b..f35051ebc 
>>> 100644
>>> --- a/lib/igt_psr.c
>>> +++ b/lib/igt_psr.c
>>> @@ -38,7 +38,7 @@ bool psr_disabled_check(int debugfs_fd)
>>>  	igt_debugfs_simple_read(debugfs_fd, "i915_edp_psr_status", buf,
>>>  				sizeof(buf));
>>> 
>>> -	return strstr(buf, "PSR mode: disabled\n");
>>Lets not change the format here. We can still keep it as PSR mode : disabled/enabled
>>> +	return strstr(buf, "PSR disabled:");
>>>  }
>>> 
>>>  bool selective_fetch_check(int debugfs_fd, igt_output_t *output) @@ 
>>> -122,6
>>> +122,8 @@ static bool psr_active_check(int debugfs_fd, enum psr_mode 
>>> +mode,
>>> igt_output_t *o
>>> 
>>>  	igt_skip_on(strstr(buf, "PSR sink not reliable: yes"));
>>> 
>>> +	igt_skip_on(strstr(buf, "PSR setup timing not met"));
>>> +
>> I think instead of printing like this. It can be:  PSR sink not reliable: yes (setup timing not met)
>
> My current understanding is that kernel on JSL reports that sink is reliable. But it disables PSR basing on the setup timing. Thus, questioned lines in i915_edp_psr_status with this change look like this:
>
> PSR mode: disabled
> PSR sink not reliable: no (PSR setup timing not met)
>
> I thought it looks a bit misleading, because it seems like we are giving the reason why the sink is reliable, and not why PSR is disabled. That's why I also changed the format, to include this case. Also, because of that, in the IGT test we would still need two different checks for skip, since "sink not reliable:" is independent of "PSR setup timing not met".
>
> What are your thoughts on this? Should we keep the reason after "sink not reliable:", change the format, or something else?

I think overall the PSR should migrate towards what we have for FBC. If
PSR is disabled, we want to know the reason.

"PSR sink not reliable: yes (setup timing not met)" is not
interesting. Moreover, "setup timing not met" is not the reason sink is
not reliable. Both "setup timing not met" *and* "sink is not reliable"
are orthogonal reasons for not enabling PSR.

I think we should go towards something like "PSR disabled: <reason>".

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-06-04 11:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 12:19 [PATCH i-g-t v1 0/2] Skip PSR when disabled Michał Grzelak
2025-05-13 12:19 ` [PATCH i-g-t v1 1/2] lib/igt_psr: Skip the test when PSR is disabled Michał Grzelak
2025-05-26  5:37   ` B, Jeevan
2025-06-02 21:24     ` Grzelak, Michal
2025-06-04 11:48       ` Jani Nikula [this message]
2025-05-13 12:19 ` [PATCH i-g-t v1 2/2] tests/intel/kms_frontbuffer_tracking: pass non-NULL output pointer Michał Grzelak
2025-05-13 17:47 ` ✗ Xe.CI.BAT: failure for Skip PSR when disabled Patchwork
2025-05-13 17:57 ` ✗ Xe.CI.Full: " Patchwork
2025-05-13 18:09 ` ✓ i915.CI.BAT: success " Patchwork
2025-05-13 21:25 ` ✗ i915.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=14806d021fac55a7145795dfd254ea3ad7171e4f@intel.com \
    --to=jani.nikula@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeevan.b@intel.com \
    --cc=michal.grzelak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.