From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org,
"Jani Nikula" <jani.nikula@intel.com>,
"Jouni Högander" <jouni.hogander@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Subject: [PATCH 0/4] drm/i915/reset: Expose "display_reset_count" in debugfs
Date: Fri, 10 Apr 2026 10:34:56 +0300 [thread overview]
Message-ID: <20260410073500.32308-1-ville.syrjala@linux.intel.com> (raw)
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Expose a display reset count in debugfs. It will be used
by kms_busy/*-with-reset tests to confirm they are actually
testing the thing they are meant to test.
I expect this to fail on all platforms using execlist
submission. I'll send a second version of the series
with a fix after confirming that.
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Jouni Högander <jouni.hogander@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Test-with: 20260409200924.5409-1-ville.syrjala@linux.intel.com
Ville Syrjälä (4):
drm/i915/reset: Reorganize display reset code
drm/i915/reset: Move pending_fb_pin handling to i915
drm/xe/display: Add init_clock_gating.h stubs
drm/i915/reset: Add "display_reset_count" debugfs file
.../gpu/drm/i915/display/intel_display_core.h | 5 ++-
.../drm/i915/display/intel_display_debugfs.c | 2 +
.../drm/i915/display/intel_display_power.c | 2 -
.../drm/i915/display/intel_display_reset.c | 40 +++++++++----------
.../drm/i915/display/intel_display_reset.h | 8 ++--
drivers/gpu/drm/i915/display/intel_overlay.c | 10 +----
drivers/gpu/drm/i915/gt/intel_reset.c | 26 +++++++-----
drivers/gpu/drm/i915/i915_dpt.c | 5 +--
drivers/gpu/drm/i915/i915_drv.h | 2 +
drivers/gpu/drm/i915/i915_fb_pin.c | 9 ++---
drivers/gpu/drm/i915/i915_overlay.c | 6 +++
drivers/gpu/drm/xe/Makefile | 1 +
.../compat-i915-headers/intel_clock_gating.h | 10 ++++-
13 files changed, 71 insertions(+), 55 deletions(-)
--
2.52.0
next reply other threads:[~2026-04-10 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 7:34 Ville Syrjala [this message]
2026-04-10 7:34 ` [PATCH 1/4] drm/i915/reset: Reorganize display reset code Ville Syrjala
2026-04-10 7:34 ` [PATCH 2/4] drm/i915/reset: Move pending_fb_pin handling to i915 Ville Syrjala
2026-04-10 7:34 ` [PATCH 3/4] drm/xe/display: Add init_clock_gating.h stubs Ville Syrjala
2026-04-10 7:35 ` [PATCH 4/4] drm/i915/reset: Add "display_reset_count" debugfs file Ville Syrjala
2026-04-10 7:42 ` Jani Nikula
2026-04-10 7:56 ` Ville Syrjälä
2026-04-10 8:46 ` Jani Nikula
2026-04-10 7:42 ` ✓ CI.KUnit: success for drm/i915/reset: Expose "display_reset_count" in debugfs Patchwork
2026-04-10 8:20 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-10 14:41 ` ✗ 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=20260410073500.32308-1-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jouni.hogander@intel.com \
--cc=maarten.lankhorst@linux.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