Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "michal.grzelak" <mgrzelak@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>,
	 "intel-xe@lists.freedesktop.org"
	<intel-xe@lists.freedesktop.org>,
	 "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Grzelak, Michal" <michal.grzelak@intel.com>,
	 "Brzezinka, Sebastian" <sebastian.brzezinka@intel.com>
Subject: Re: [PATCH v10 1/1] drm/i915/display: Add no_psr_reason to PSR debugfs
Date: Mon, 15 Sep 2025 15:30:45 +0200 (CEST)	[thread overview]
Message-ID: <497eb7e8-0fa4-c0be-bfb2-7ff33c5afd79@intel.com> (raw)
In-Reply-To: <ad14c2fd3d8e505f835cdb59daf1cbff5fb3ed9c.camel@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

On Mon, 15 Sep 2025, Hogander, Jouni wrote:

> On Wed, 2025-09-03 at 12:31 +0200, Michał Grzelak wrote:
>> There is no reason in debugfs why PSR has been disabled. Currently,
>> without this information, IGT tests cannot decide whether PSR has
>> been disabled on purpose or was it abnormal behavior. Because of it,
>> the status of the test cannot be decided correctly.
>>
>> Add no_psr_reason field into struct intel_psr. Add no_psr_reason
>> into struct intel_crtc_state to prevent staying out of sync when
>> _psr_compute_config is not using computed state. Write the reason,
>> e.g. PSR setup timing not met, into proper PSR debugfs file. Update
>> the reason from old_crtc_state in intel_psr_pre_plane_update. Extend
>> format of debugfs file to have reason when it is non-NULL. Clean the
>> reason when PSR is activated.
>>
>> Refactor intel_psr_post_plane_update to use no_psr_reason along
>> keep_disabled.
>> [...]
>> @@ -2922,6 +2924,9 @@ void intel_psr_pre_plane_update(struct
>> intel_atomic_state *state,
>>  
>>  		mutex_lock(&psr->lock);
>>  
>> +		if (!new_crtc_state->has_psr)
>> +			psr->no_psr_reason = old_crtc_state-
>>> no_psr_reason;
>
> I think you should use new_crtc_state->no_psr_reason.
>
Right, thanks for picking that. Will fix it in next version.

BR,
Michał

  reply	other threads:[~2025-09-15 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 10:31 [PATCH v10 0/1] drm/i915/display: Add no_psr_reason to PSR debugfs Michał Grzelak
2025-09-03 10:31 ` [PATCH v10 1/1] " Michał Grzelak
2025-09-15 12:07   ` Hogander, Jouni
2025-09-15 13:30     ` michal.grzelak [this message]
2025-09-03 11:02 ` ✓ CI.KUnit: success for drm/i915/display: Add no_psr_reason to PSR debugfs (rev13) Patchwork
2025-09-03 11:52 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-03 18:32 ` ✗ Xe.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=497eb7e8-0fa4-c0be-bfb2-7ff33c5afd79@intel.com \
    --to=mgrzelak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jouni.hogander@intel.com \
    --cc=michal.grzelak@intel.com \
    --cc=sebastian.brzezinka@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