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 v1 0/1] drm/i915/display: Add no_psr_reason to PSR debugfs
Date: Tue, 13 May 2025 13:35:25 +0200 [thread overview]
Message-ID: <20250513113526.2758433-1-michal.grzelak@intel.com> (raw)
This patch handles failed PSR tests seen on JSL. It should be tested in
parallel with proper IGT change; since both kernel and IGT changes
depend on each another, there is possibility the tag to the IGT change
will not be picked by Patchwork. In that case, v2's cover letter for
the kernel patch will include tag to the proper IGT series.
Test-with: <20250509232659.2721697-1-michal.grzelak@intel.com>
Best regards,
Michał
Michał Grzelak (1):
drm/i915/display: Add no_psr_reason to PSR debugfs
.../gpu/drm/i915/display/intel_display_types.h | 2 ++
drivers/gpu/drm/i915/display/intel_psr.c | 15 ++++++++-------
2 files changed, 10 insertions(+), 7 deletions(-)
--
2.45.2
next reply other threads:[~2025-05-13 11:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 11:35 Michał Grzelak [this message]
2025-05-13 11:35 ` [PATCH v1 1/1] drm/i915/display: Add no_psr_reason to PSR debugfs Michał Grzelak
2025-05-13 12:23 ` Jani Nikula
2025-05-14 9:41 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-14 9:41 ` ✓ CI.checkpatch: " Patchwork
2025-05-14 9:42 ` ✓ CI.KUnit: " Patchwork
2025-05-14 9:52 ` ✓ CI.Build: " Patchwork
2025-05-14 9:55 ` ✓ CI.Hooks: " Patchwork
2025-05-14 9:56 ` ✓ CI.checksparse: " Patchwork
2025-05-14 10:32 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-14 14:11 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-26 23:16 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-26 23:16 ` ✓ CI.checkpatch: " Patchwork
2025-05-26 23:17 ` ✓ CI.KUnit: " Patchwork
2025-05-26 23:27 ` ✓ CI.Build: " 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=20250513113526.2758433-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