From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/4] drm/{i915, xe}: convert i915->display and xe->display into pointers
Date: Wed, 7 May 2025 12:38:32 +0300 [thread overview]
Message-ID: <cover.1746610601.git.jani.nikula@intel.com> (raw)
Another small step towards separating i915 and xe drivers from
display. Convert the i915->display and xe->display members into
pointers. In the future, we can allocate them dynamically, but one step
at a time.
BR,
Jani.
Jani Nikula (4):
drm/xe/rpm: use to_xe_device() instead of container_of
drm/xe/display: do not reference xe->display inline
drm/i915: do not reference i915->display inline
drm/{i915,xe}: convert i915 and xe display members into pointers
.../i915/display/intel_display_conversion.c | 2 +-
drivers/gpu/drm/i915/display/intel_dpt.c | 2 +-
drivers/gpu/drm/i915/display/intel_vbt_defs.h | 2 +-
.../i915/gem/i915_gem_object_frontbuffer.h | 2 +-
drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c | 2 +-
drivers/gpu/drm/i915/gt/intel_gt_pm.c | 4 +-
drivers/gpu/drm/i915/gt/intel_reset.c | 4 +-
drivers/gpu/drm/i915/gt/intel_rps.c | 4 +-
drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 +-
drivers/gpu/drm/i915/gvt/display.c | 10 ++--
drivers/gpu/drm/i915/gvt/fb_decoder.c | 6 +-
drivers/gpu/drm/i915/gvt/handlers.c | 8 +--
drivers/gpu/drm/i915/i915_driver.c | 57 ++++++++++--------
drivers/gpu/drm/i915/i915_drv.h | 3 +-
drivers/gpu/drm/i915/i915_getparam.c | 2 +-
drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
drivers/gpu/drm/i915/i915_irq.c | 50 ++++++++--------
drivers/gpu/drm/i915/intel_clock_gating.c | 3 +-
drivers/gpu/drm/xe/display/xe_display.c | 60 +++++++++++--------
drivers/gpu/drm/xe/display/xe_display_rpm.c | 3 +-
drivers/gpu/drm/xe/display/xe_fb_pin.c | 5 +-
drivers/gpu/drm/xe/xe_device_types.h | 3 +-
22 files changed, 130 insertions(+), 110 deletions(-)
--
2.39.5
next reply other threads:[~2025-05-07 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 9:38 Jani Nikula [this message]
2025-05-07 9:38 ` [PATCH 1/4] drm/xe/rpm: use to_xe_device() instead of container_of Jani Nikula
2025-05-07 9:38 ` [PATCH 2/4] drm/xe/display: do not reference xe->display inline Jani Nikula
2025-05-07 9:38 ` [PATCH 3/4] drm/i915: do not reference i915->display inline Jani Nikula
2025-05-07 9:38 ` [PATCH 4/4] drm/{i915, xe}: convert i915 and xe display members into pointers Jani Nikula
2025-05-07 15:22 ` [PATCH v2] " Jani Nikula
2025-05-07 12:54 ` [PATCH 0/4] drm/{i915, xe}: convert i915->display and xe->display " Gustavo Sousa
2025-05-16 8:32 ` Jani Nikula
2025-05-07 17:04 ` ✓ CI.Patch_applied: success for drm/{i915, xe}: convert i915->display and xe->display into pointers (rev2) Patchwork
2025-05-07 17:05 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-07 17:06 ` ✓ CI.KUnit: success " Patchwork
2025-05-07 17:14 ` ✓ CI.Build: " Patchwork
2025-05-07 17:17 ` ✓ CI.Hooks: " Patchwork
2025-05-07 17:18 ` ✓ CI.checksparse: " Patchwork
2025-05-07 17:41 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-08 13:27 ` ✓ Xe.CI.Full: " Patchwork
2025-05-26 17:23 ` ✗ CI.Patch_applied: 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.1746610601.git.jani.nikula@intel.com \
--to=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).