From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, matthew.d.roper@intel.com
Subject: [PATCH v3 0/8] drm/i915: display reset cleanups
Date: Mon, 3 Mar 2025 13:27:02 +0200 [thread overview]
Message-ID: <cover.1741001054.git.jani.nikula@intel.com> (raw)
v3 of [1], removing I915_RESET_MODESET flag altogether for even further
simplification.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1740481927.git.jani.nikula@intel.com
Jani Nikula (8):
drm/i915/display: convert display reset to struct intel_display *
drm/i915: move pending_fb_pin to struct intel_display
drm/i915/reset: add intel_gt_gpu_reset_clobbers_display() helper
drm/i915/reset: add intel_display_reset_test()
drm/i915/reset: remove I915_RESET_MODESET flag
drm/i915/reset: decide whether display reset is needed on gt side
drm/i915/reset: pass test only parameter to
intel_display_reset_finish()
drm/i915/reset: add modeset_stuck callback to
intel_display_reset_prepare()
.../gpu/drm/i915/display/intel_display_core.h | 2 +
.../drm/i915/display/intel_display_reset.c | 73 ++++++++-----------
.../drm/i915/display/intel_display_reset.h | 12 ++-
drivers/gpu/drm/i915/display/intel_dpt.c | 5 +-
drivers/gpu/drm/i915/display/intel_fb_pin.c | 10 ++-
drivers/gpu/drm/i915/display/intel_overlay.c | 5 +-
drivers/gpu/drm/i915/gt/intel_engine_cs.c | 2 +-
drivers/gpu/drm/i915/gt/intel_gt_pm.c | 2 +-
drivers/gpu/drm/i915/gt/intel_reset.c | 41 +++++++++--
drivers/gpu/drm/i915/gt/intel_reset.h | 2 +
drivers/gpu/drm/i915/gt/intel_reset_types.h | 3 +-
drivers/gpu/drm/i915/i915_driver.c | 2 +-
drivers/gpu/drm/i915/i915_gpu_error.h | 2 -
13 files changed, 92 insertions(+), 69 deletions(-)
--
2.39.5
next reply other threads:[~2025-03-03 11:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 11:27 Jani Nikula [this message]
2025-03-03 11:27 ` [PATCH v3 1/8] drm/i915/display: convert display reset to struct intel_display * Jani Nikula
2025-03-03 11:27 ` [PATCH v3 2/8] drm/i915: move pending_fb_pin to struct intel_display Jani Nikula
2025-03-03 11:27 ` [PATCH v3 3/8] drm/i915/reset: add intel_gt_gpu_reset_clobbers_display() helper Jani Nikula
2025-03-03 11:27 ` [PATCH v3 4/8] drm/i915/reset: add intel_display_reset_test() Jani Nikula
2025-03-03 11:27 ` [PATCH v3 5/8] drm/i915/reset: remove I915_RESET_MODESET flag Jani Nikula
2025-03-03 23:11 ` Matt Roper
2025-03-03 11:27 ` [PATCH v3 6/8] drm/i915/reset: decide whether display reset is needed on gt side Jani Nikula
2025-03-03 23:15 ` Matt Roper
2025-03-03 11:27 ` [PATCH v3 7/8] drm/i915/reset: pass test only parameter to intel_display_reset_finish() Jani Nikula
2025-03-03 23:21 ` Matt Roper
2025-03-03 11:27 ` [PATCH v3 8/8] drm/i915/reset: add modeset_stuck callback to intel_display_reset_prepare() Jani Nikula
2025-03-03 23:22 ` Matt Roper
2025-03-03 11:51 ` ✓ CI.Patch_applied: success for drm/i915: display reset cleanups (rev2) Patchwork
2025-03-03 11:51 ` ✓ CI.checkpatch: " Patchwork
2025-03-03 11:53 ` ✓ CI.KUnit: " Patchwork
2025-03-03 12:09 ` ✓ CI.Build: " Patchwork
2025-03-03 12:11 ` ✓ CI.Hooks: " Patchwork
2025-03-03 12:13 ` ✗ CI.checksparse: warning " Patchwork
2025-03-03 12:33 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-03 13:56 ` ✗ 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=cover.1741001054.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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