From: Matt Roper <matthew.d.roper@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH 00/10] Engine initialization cleanup
Date: Thu, 23 Apr 2026 15:48:47 -0700 [thread overview]
Message-ID: <20260423-engine-setup-v1-0-baa94014e3e5@intel.com> (raw)
A lot of our engine initialization code was inherited from i915 and
hasn't received too much cleanup since that time. There's also some
inconsistencies between the main initialization path used on all
platforms, and the vestigial execlist code which isn't actually used but
still remains in the driver as dead code for now. Let's clean things up
a bit and, where possible, move the required engine programming into the
RTP infrastructure so that it will be applied on both initialization
paths, and be dumpable/checkable via debugfs.
There's some more restructuring that should happen to more clearly
distinguish software state initialization from hardware initialization
(and re-initialization on various resets & suspend/resume), but I'll
leave that to a follow-up series to prevent this one from getting too
complicated.
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
---
Matt Roper (10):
drm/xe: Move CCS enablement to engine setup RTP
drm/xe/rtp: Add "always true" match function
drm/xe: Stop programming BLIT_CCTL on Xe2 and later platforms
drm/xe: Move HWSTAM programming to RTP
drm/xe: Fix name and definition of GFX_MODE register
drm/xe: Const-ify parameters to xe_device_has_* functions
drm/xe: Move GFX_MODE programming to RTP
drm/xe: Drop unnecessary STOP_RING clearing
drm/xe: Drop xe_hw_engine_mmio_write32()
drm/xe: Mark BCS engines as belonging to the GT forcewake domain
drivers/gpu/drm/xe/regs/xe_engine_regs.h | 5 +-
drivers/gpu/drm/xe/xe_device.h | 14 +++---
drivers/gpu/drm/xe/xe_execlist.c | 9 ----
drivers/gpu/drm/xe/xe_guc_ads.c | 2 -
drivers/gpu/drm/xe/xe_guc_capture.c | 2 +-
drivers/gpu/drm/xe/xe_hw_engine.c | 82 +++++++++++++-------------------
drivers/gpu/drm/xe/xe_lrc.c | 20 --------
drivers/gpu/drm/xe/xe_rtp.c | 15 ++++++
drivers/gpu/drm/xe/xe_rtp.h | 24 ++++++++++
9 files changed, 81 insertions(+), 92 deletions(-)
---
base-commit: 021ccd6f29b34f09e4b3aac0d6d52b8adaa1c4b4
change-id: 20260402-engine-setup-e66851295e18
Best regards,
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next reply other threads:[~2026-04-23 22:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 22:48 Matt Roper [this message]
2026-04-23 22:48 ` [PATCH 01/10] drm/xe: Move CCS enablement to engine setup RTP Matt Roper
2026-04-24 19:21 ` Matt Roper
2026-04-23 22:48 ` [PATCH 02/10] drm/xe/rtp: Add "always true" match function Matt Roper
2026-04-24 17:17 ` Lin, Shuicheng
2026-04-23 22:48 ` [PATCH 03/10] drm/xe: Stop programming BLIT_CCTL on Xe2 and later platforms Matt Roper
2026-04-23 22:48 ` [PATCH 04/10] drm/xe: Move HWSTAM programming to RTP Matt Roper
2026-04-24 18:15 ` Lin, Shuicheng
2026-04-23 22:48 ` [PATCH 05/10] drm/xe: Fix name and definition of GFX_MODE register Matt Roper
2026-04-23 22:48 ` [PATCH 06/10] drm/xe: Const-ify parameters to xe_device_has_* functions Matt Roper
2026-04-24 7:27 ` Michal Wajdeczko
2026-04-23 22:48 ` [PATCH 07/10] drm/xe: Move GFX_MODE programming to RTP Matt Roper
2026-04-24 17:24 ` Lin, Shuicheng
2026-04-23 22:48 ` [PATCH 08/10] drm/xe: Drop unnecessary STOP_RING clearing Matt Roper
2026-04-23 22:48 ` [PATCH 09/10] drm/xe: Drop xe_hw_engine_mmio_write32() Matt Roper
2026-04-24 17:06 ` Lin, Shuicheng
2026-04-23 22:48 ` [PATCH 10/10] drm/xe: Mark BCS engines as belonging to the GT forcewake domain Matt Roper
2026-04-24 16:46 ` Lin, Shuicheng
2026-04-23 22:56 ` ✓ CI.KUnit: success for Engine initialization cleanup Patchwork
2026-04-23 23:44 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-04-24 5:34 ` ✓ Xe.CI.FULL: success " 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=20260423-engine-setup-v1-0-baa94014e3e5@intel.com \
--to=matthew.d.roper@intel.com \
--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