From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, rodrigo.vivi@intel.com,
lucas.demarchi@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH 0/4] drm/{i915,xe}: Move PCH stuff under display
Date: Fri, 11 Apr 2025 12:54:10 +0300 [thread overview]
Message-ID: <cover.1744364975.git.jani.nikula@intel.com> (raw)
Resurrect [1], patches 1-2 unchanged, with some cleanups on top.
With the current patches in flight, we'll have removed all the PCH
checks from i915 core other than a couple of instances in
intel_clock_gating.c. We can figure those out as we go along, but
merging this now unblocks a bunch of further cleanups in display.
BR,
Jani.
[1] https://lore.kernel.org/r/20250218010224.761209-1-rodrigo.vivi@intel.com
Jani Nikula (2):
drm/i915/pch: move PCH detection to intel_display_driver_early_probe()
drm/i915/pch: clean up includes
Rodrigo Vivi (2):
drm/{i915,xe}: Move intel_pch under display
drm/i915/display: Convert intel_pch towards intel_display
drivers/gpu/drm/i915/Makefile | 2 +-
.../gpu/drm/i915/display/intel_display_core.h | 6 +-
.../drm/i915/display/intel_display_driver.c | 3 +
.../gpu/drm/i915/{soc => display}/intel_pch.c | 248 +++++++++---------
drivers/gpu/drm/i915/display/intel_pch.h | 58 ++++
drivers/gpu/drm/i915/i915_driver.c | 3 -
drivers/gpu/drm/i915/i915_drv.h | 5 -
drivers/gpu/drm/i915/soc/intel_pch.h | 56 ----
drivers/gpu/drm/xe/Makefile | 2 +-
.../xe/compat-i915-headers/soc/intel_pch.h | 6 -
drivers/gpu/drm/xe/display/xe_display.c | 3 -
drivers/gpu/drm/xe/xe_device_types.h | 2 -
12 files changed, 199 insertions(+), 195 deletions(-)
rename drivers/gpu/drm/i915/{soc => display}/intel_pch.c (50%)
create mode 100644 drivers/gpu/drm/i915/display/intel_pch.h
delete mode 100644 drivers/gpu/drm/i915/soc/intel_pch.h
delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/soc/intel_pch.h
--
2.39.5
next reply other threads:[~2025-04-11 9:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:54 Jani Nikula [this message]
2025-04-11 9:54 ` [PATCH 1/4] drm/{i915,xe}: Move intel_pch under display Jani Nikula
2025-04-11 14:15 ` Lucas De Marchi
2025-04-11 9:54 ` [PATCH 2/4] drm/i915/display: Convert intel_pch towards intel_display Jani Nikula
2025-04-11 14:17 ` Lucas De Marchi
2025-04-14 8:14 ` Jani Nikula
2025-04-11 9:54 ` [PATCH 3/4] drm/i915/pch: move PCH detection to intel_display_driver_early_probe() Jani Nikula
2025-04-11 14:18 ` Lucas De Marchi
2025-04-11 9:54 ` [PATCH 4/4] drm/i915/pch: clean up includes Jani Nikula
2025-04-11 14:21 ` Lucas De Marchi
2025-04-11 10:00 ` ✓ CI.Patch_applied: success for drm/{i915,xe}: Move PCH stuff under display Patchwork
2025-04-11 10:00 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-11 10:01 ` ✓ CI.KUnit: success " Patchwork
2025-04-11 10:14 ` ✓ CI.Build: " Patchwork
2025-04-11 10:17 ` ✓ CI.Hooks: " Patchwork
2025-04-11 10:19 ` ✓ CI.checksparse: " Patchwork
2025-04-11 11:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-11 11:33 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-04-11 11:33 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-11 11:56 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-11 12:46 ` ✓ Xe.CI.Full: " Patchwork
2025-04-11 14:07 ` ✓ i915.CI.Full: " 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.1744364975.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.