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 v2 0/5] drm/{i915, xe}: move fbdev fb calls to parent interface
Date: Tue, 31 Mar 2026 12:49:13 +0300 [thread overview]
Message-ID: <cover.1774950508.git.jani.nikula@intel.com> (raw)
Rebase of [1] on top of the AuxCCS changes, after some merges and
backmerges.
[1] https://lore.kernel.org/r/cover.1773840563.git.jani.nikula@intel.com
Jani Nikula (5):
drm/xe/fbdev: put intel_fbdev_fb_prefer_stolen() behind
IS_ENABLED(CONFIG_DRM_FBDEV_EMULATION)
drm/{i915,xe}/fbdev: drop drm device parameter from
intel_fbdev_fb_fill_info()
drm/{i915,xe}: move fbdev fb calls to parent interface
drm/i915: pass struct drm_i915_private to
i915_bo_fbdev_prefer_stolen()
drm/xe: pass struct xe_device to xe_display_bo_fbdev_prefer_stolen()
drivers/gpu/drm/i915/Makefile | 3 +-
drivers/gpu/drm/i915/display/intel_bo.c | 27 ++++
drivers/gpu/drm/i915/display/intel_bo.h | 8 ++
drivers/gpu/drm/i915/display/intel_fbdev.c | 14 +-
drivers/gpu/drm/i915/display/intel_fbdev_fb.c | 118 -----------------
drivers/gpu/drm/i915/display/intel_fbdev_fb.h | 24 ----
drivers/gpu/drm/i915/i915_bo.c | 114 +++++++++++++++++
drivers/gpu/drm/i915/i915_bo.h | 6 +
drivers/gpu/drm/i915/i915_initial_plane.c | 4 +-
drivers/gpu/drm/xe/Makefile | 1 -
drivers/gpu/drm/xe/display/intel_fbdev_fb.c | 120 ------------------
drivers/gpu/drm/xe/display/xe_display_bo.c | 120 ++++++++++++++++++
drivers/gpu/drm/xe/display/xe_display_bo.h | 6 +
drivers/gpu/drm/xe/display/xe_initial_plane.c | 5 +-
include/drm/intel/display_parent_interface.h | 7 +
15 files changed, 301 insertions(+), 276 deletions(-)
delete mode 100644 drivers/gpu/drm/i915/display/intel_fbdev_fb.c
delete mode 100644 drivers/gpu/drm/i915/display/intel_fbdev_fb.h
delete mode 100644 drivers/gpu/drm/xe/display/intel_fbdev_fb.c
--
2.47.3
next reply other threads:[~2026-03-31 9:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 9:49 Jani Nikula [this message]
2026-03-31 9:49 ` [PATCH v2 1/5] drm/xe/fbdev: put intel_fbdev_fb_prefer_stolen() behind IS_ENABLED(CONFIG_DRM_FBDEV_EMULATION) Jani Nikula
2026-03-31 9:49 ` [PATCH v2 2/5] drm/{i915, xe}/fbdev: drop drm device parameter from intel_fbdev_fb_fill_info() Jani Nikula
2026-03-31 9:49 ` [PATCH v2 3/5] drm/{i915, xe}: move fbdev fb calls to parent interface Jani Nikula
2026-03-31 9:49 ` [PATCH v2 4/5] drm/i915: pass struct drm_i915_private to i915_bo_fbdev_prefer_stolen() Jani Nikula
2026-03-31 9:49 ` [PATCH v2 5/5] drm/xe: pass struct xe_device to xe_display_bo_fbdev_prefer_stolen() Jani Nikula
2026-03-31 10:03 ` ✗ CI.checkpatch: warning for drm/{i915, xe}: move fbdev fb calls to parent interface Patchwork
2026-03-31 10:04 ` ✓ CI.KUnit: success " Patchwork
2026-03-31 10:39 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-31 11:06 ` ✓ i915.CI.BAT: success " Patchwork
2026-03-31 14:38 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-31 22:48 ` ✗ i915.CI.Full: failure " Patchwork
2026-04-01 9:45 ` ✗ CI.checkpatch: warning for drm/{i915, xe}: move fbdev fb calls to parent interface (rev2) Patchwork
2026-04-01 9:46 ` ✓ CI.KUnit: success " Patchwork
2026-04-01 10:35 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-01 12:47 ` ✓ i915.CI.BAT: " Patchwork
2026-04-01 15:48 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-02 5:07 ` ✓ i915.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=cover.1774950508.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 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.