Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Grzelak" <michal.grzelak@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Michał Grzelak" <michal.grzelak@intel.com>
Subject: [PATCH v3 RERUN 0/1] drm/i915/display: Add no_psr_reason to PSR debugfs
Date: Tue,  1 Jul 2025 19:02:33 +0200	[thread overview]
Message-ID: <20250701170234.443586-1-michal.grzelak@intel.com> (raw)

Rerun of v3 [1]. 

[1] https://lore.kernel.org/intel-gfx/20250624164823.4118263-1-michal.grzelak@intel.com

Test-with: <20250701165913.443515-2-michal.grzelak@intel.com>

Best regards,
Michał

---
Changelog:
v2->v3
- change reason description to be more specific [Mika]
- remove BSpecs number & WA number from being written into no_psr_reason
- replace spaces with tabs
- provide correct Test-with tag to the IGT patch, instead of series

v1->v2
- set other reasons than "PSR setup timing not met"
- clear no_psr_reason when activating PSR.

Michał Grzelak (1):
  drm/i915/display: Add no_psr_reason to PSR debugfs

 .../drm/i915/display/intel_display_types.h    |  2 +
 drivers/gpu/drm/i915/display/intel_psr.c      | 38 ++++++++++++-------
 2 files changed, 26 insertions(+), 14 deletions(-)

-- 
2.45.2


             reply	other threads:[~2025-07-01 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 17:02 Michał Grzelak [this message]
2025-07-01 17:02 ` [PATCH v3 RERUN 1/1] drm/i915/display: Add no_psr_reason to PSR debugfs Michał Grzelak
2025-07-01 17:09 ` ✓ CI.KUnit: success for drm/i915/display: Add no_psr_reason to PSR debugfs (rev5) Patchwork
2025-07-02  6:52 ` ✓ CI.KUnit: success for drm/i915/display: Add no_psr_reason to PSR debugfs (rev6) Patchwork
2025-07-02  7:30 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-03 10:49 ` ✗ Xe.CI.Full: failure for drm/i915/display: Add no_psr_reason to PSR debugfs (rev5) Patchwork
2025-07-03 20:54 ` ✗ Xe.CI.Full: failure for drm/i915/display: Add no_psr_reason to PSR debugfs (rev6) 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=20250701170234.443586-1-michal.grzelak@intel.com \
    --to=michal.grzelak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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