From: David Kershner <david.kershner@intel.com>
To: david.kershner@intel.com, intel-xe@lists.freedesktop.org,
michael.j.ruhl@intel.com, john.fleck@intel.com,
lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
matthew.d.roper@intel.com, matthew.brost@intel.com
Subject: [Intel-xe] [PATCH 0/3] Add support for XeLink device
Date: Tue, 8 Aug 2023 12:45:31 -0400 [thread overview]
Message-ID: <20230808164534.1027552-1-david.kershner@intel.com> (raw)
First patch set introduce the needed Xe infrastructure to support
XeLink device.
The XeLink device is a glue-less module attached to a GPU device that
provides connectivity between different GPUs on the same system.
The XeLink is part of the GPU (the register space is part of the GPU
PCIe BAR), so it cannot be a completely separate device driver.
The Linux kernel provides an interface for handling this type of
device, the Auxiliary Bus API.
The Xe and XeLink will use the auxiliary bus to enable the XeLink
and the Xe to probe and communicate.
A followup series will include the XeLink driver code to provide
full functionality for the device.
David Kershner (3):
drm/xe: Introduce a module parameter to control XeLink
drm/xe: Introduce XeLink device
drm/xe: Teach i915 how to use objects with XeLink connectivity
drivers/gpu/drm/xe/Kconfig | 1 +
drivers/gpu/drm/xe/Makefile | 3 +-
drivers/gpu/drm/xe/regs/xe_gt_regs.h | 20 ++
drivers/gpu/drm/xe/xe_bo.c | 47 ++-
drivers/gpu/drm/xe/xe_bo.h | 2 +
drivers/gpu/drm/xe/xe_device.c | 13 +-
drivers/gpu/drm/xe/xe_device_types.h | 27 ++
drivers/gpu/drm/xe/xe_dma_buf.c | 162 ++++++---
drivers/gpu/drm/xe/xe_dma_buf.h | 3 +
drivers/gpu/drm/xe/xe_gt_types.h | 2 +
drivers/gpu/drm/xe/xe_irq.c | 28 +-
drivers/gpu/drm/xe/xe_mmio.c | 2 +-
drivers/gpu/drm/xe/xe_pci.c | 2 +
drivers/gpu/drm/xe/xe_pci_types.h | 1 +
drivers/gpu/drm/xe/xe_pt.c | 7 +-
drivers/gpu/drm/xe/xe_xelink.c | 476 +++++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_xelink.h | 38 +++
include/drm/intel_xelink_platform.h | 140 ++++++++
18 files changed, 921 insertions(+), 53 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_xelink.c
create mode 100644 drivers/gpu/drm/xe/xe_xelink.h
create mode 100644 include/drm/intel_xelink_platform.h
--
2.35.1
next reply other threads:[~2023-08-08 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 16:45 David Kershner [this message]
2023-08-08 16:45 ` [Intel-xe] [PATCH 1/3] drm/xe: Introduce a module parameter to control XeLink David Kershner
2023-08-08 18:43 ` Rodrigo Vivi
2023-08-09 10:26 ` Jani Nikula
2023-08-10 22:17 ` Rodrigo Vivi
2023-08-09 3:19 ` Matthew Brost
2023-08-08 16:45 ` [Intel-xe] [PATCH 2/3] drm/xe: Introduce XeLink device David Kershner
2023-08-08 18:43 ` Rodrigo Vivi
2023-08-08 16:45 ` [Intel-xe] [PATCH 3/3] drm/xe: Teach i915 how to use objects with XeLink connectivity David Kershner
2023-08-08 18:41 ` Rodrigo Vivi
-- strict thread matches above, loose matches on Subject: below --
2023-11-20 18:56 [Intel-xe] [PATCH 0/3] Add support for XeLink device David Kershner
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=20230808164534.1027552-1-david.kershner@intel.com \
--to=david.kershner@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.fleck@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michael.j.ruhl@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