Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 0/2] Prepare intel_fbdev for Xe
Date: Wed, 15 Nov 2023 11:07:17 +0200	[thread overview]
Message-ID: <20231115090719.3210079-1-jouni.hogander@intel.com> (raw)

Intel_fbdev buffer allocation and it's backing object handling differs
a lot between i915 and Xe. 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. This is needed because i915_gem_object and
xe_bo implementations are differing.

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 (2):
  drm/i915/display: split i915 specific code from intel_fbdev
  drm/i915/display: use intel_bo_to_drm_bo in intel_fbdev

 drivers/gpu/drm/i915/Makefile                 |   3 +-
 drivers/gpu/drm/i915/display/intel_fbdev.c    | 112 ++---------------
 drivers/gpu/drm/i915/display/intel_fbdev_fb.c | 115 ++++++++++++++++++
 drivers/gpu/drm/i915/display/intel_fbdev_fb.h |  21 ++++
 4 files changed, 148 insertions(+), 103 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/display/intel_fbdev_fb.c
 create mode 100644 drivers/gpu/drm/i915/display/intel_fbdev_fb.h

-- 
2.34.1


             reply	other threads:[~2023-11-15  9:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15  9:07 Jouni Högander [this message]
2023-11-15  9:07 ` [Intel-gfx] [PATCH 1/2] drm/i915/display: split i915 specific code from intel_fbdev Jouni Högander
2023-12-01 13:53   ` Govindapillai, Vinod
2023-12-01 15:23     ` Hogander, Jouni
2023-11-15  9:07 ` [Intel-gfx] [PATCH 2/2] drm/i915/display: use intel_bo_to_drm_bo in intel_fbdev Jouni Högander
2023-12-01 13:55   ` Govindapillai, Vinod
2023-12-01 15:31     ` Hogander, Jouni
2023-11-15 12:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Prepare intel_fbdev for Xe Patchwork
2023-11-15 12:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-15 13:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-16  0:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Prepare intel_fbdev for Xe (rev2) Patchwork
2023-11-16  0:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-16  0:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-17  5:17 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-12-01 15:19   ` Hogander, Jouni

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=20231115090719.3210079-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