All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: <jouni.hogander@intel.com>
Subject: Re: [PATCH v9 1/1] drm/i915/display: Add no_psr_reason to PSR debugfs
Date: Tue, 2 Sep 2025 13:27:39 +0000	[thread overview]
Message-ID: <DCICLDOBYASE.12PDTHVNECTUV@intel.com> (raw)
In-Reply-To: <20250901170003.1582933-2-michal.grzelak@intel.com>

Hi Miachał

On Mon Sep 1, 2025 at 5:00 PM UTC, 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. Ensure
> no_psr_reason is up-to-date or NULL by resetting it at the beginning of
> intel_psr_compute_config. Clean it when PSR is activated.
>
> Refactor intel_psr_post_plane_update to use no_psr_reason along
> keep_disabled.
LGTM
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
-- 
Best regards,
Sebastian


  reply	other threads:[~2025-09-02 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 17:00 [PATCH v9 0/1] drm/i915/display: Add no_psr_reason to PSR debugfs Michał Grzelak
2025-09-01 17:00 ` [PATCH v9 1/1] " Michał Grzelak
2025-09-02 13:27   ` Sebastian Brzezinka [this message]
2025-09-03  5:35   ` Hogander, Jouni
2025-09-01 17:05 ` ✓ CI.KUnit: success for drm/i915/display: Add no_psr_reason to PSR debugfs (rev12) Patchwork
2025-09-01 17:39 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-01 18:20 ` ✓ i915.CI.BAT: success for drm/i915/display: Add no_psr_reason to PSR debugfs Patchwork
2025-09-01 21:58 ` ✓ Xe.CI.Full: success for drm/i915/display: Add no_psr_reason to PSR debugfs (rev12) Patchwork
2025-09-01 23:29 ` ✗ i915.CI.Full: failure for drm/i915/display: Add no_psr_reason to PSR debugfs 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=DCICLDOBYASE.12PDTHVNECTUV@intel.com \
    --to=sebastian.brzezinka@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jouni.hogander@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.