From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH v4 0/3] Prepare intel_fb for Xe
Date: Mon, 20 Nov 2023 12:08:30 +0200 [thread overview]
Message-ID: <20231120100833.3221946-1-jouni.hogander@intel.com> (raw)
Intel fb creation is differing between Xe and i915 due to different
implementations of backing object. This patch set is splitting i915
specific code into it's own source file. Similar source files will be
introduced for Xe as well.
Also use intel_bo_to_drm_bo instead of directly referring
i915_gem_object->base. One i915_gem_object_put is changed to
drm_gem_object_put.
v4: Move drm_any_plane_has_format check into intel_fb_bo.c
v3: Fix failure handling in intel_framebuffer_init
v2: Couple of fixes to error value handling
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Uma Shankar <uma.shankar@intel.com>
Jouni Högander (3):
drm/i915/display: use intel_bo_to_drm_bo in intel_fb.c
drm/i915/display: Convert intel_fb_modifier_to_tiling as non-static
drm/i915/display: Split i915 specific code away from intel_fb.c
drivers/gpu/drm/i915/Makefile | 1 +
drivers/gpu/drm/i915/display/intel_fb.c | 128 ++++++---------------
drivers/gpu/drm/i915/display/intel_fb.h | 2 +
drivers/gpu/drm/i915/display/intel_fb_bo.c | 102 ++++++++++++++++
drivers/gpu/drm/i915/display/intel_fb_bo.h | 24 ++++
5 files changed, 162 insertions(+), 95 deletions(-)
create mode 100644 drivers/gpu/drm/i915/display/intel_fb_bo.c
create mode 100644 drivers/gpu/drm/i915/display/intel_fb_bo.h
--
2.34.1
next reply other threads:[~2023-11-20 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 10:08 Jouni Högander [this message]
2023-11-20 10:08 ` [Intel-gfx] [PATCH v4 1/3] drm/i915/display: use intel_bo_to_drm_bo in intel_fb.c Jouni Högander
2023-11-20 10:08 ` [Intel-gfx] [PATCH v4 2/3] drm/i915/display: Convert intel_fb_modifier_to_tiling as non-static Jouni Högander
2023-11-20 14:19 ` Ville Syrjälä
2023-11-21 7:35 ` Hogander, Jouni
2023-11-21 8:39 ` Ville Syrjälä
2023-11-20 10:08 ` [Intel-gfx] [PATCH v4 3/3] drm/i915/display: Split i915 specific code away from intel_fb.c Jouni Högander
2023-11-20 14:23 ` Ville Syrjälä
2023-11-21 7:40 ` Hogander, Jouni
2023-11-21 8:51 ` Ville Syrjälä
2023-11-21 8:57 ` Hogander, Jouni
2023-11-21 9:07 ` Ville Syrjälä
2023-11-20 23:19 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Prepare intel_fb for Xe (rev4) Patchwork
2023-11-20 23:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-20 23:33 ` [Intel-gfx] ✓ Fi.CI.BAT: 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=20231120100833.3221946-1-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@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