[PATCH v3 0/3] Add support for XeLink device

[Kershner, David]

> -----Original Message-----
> From: De Marchi, Lucas <lucas.demarchi at intel.com>
> Sent: Friday, December 15, 2023 11:38 AM
> To: Ruhl, Michael J <michael.j.ruhl at intel.com>
> Cc: Kershner, David <david.kershner at intel.com>; intel-
> xe at lists.freedesktop.org; Fleck, John <john.fleck at intel.com>; Vivi, Rodrigo
> <rodrigo.vivi at intel.com>; Roper, Matthew D <matthew.d.roper at intel.com>
> Subject: Re: [PATCH v3 0/3] Add support for XeLink device
> 
> On Fri, Dec 15, 2023 at 02:50:25PM +0000, Ruhl, Michael J wrote:
> >>-----Original Message-----
> >>From: Kershner, David <david.kershner at intel.com>
> >>Sent: Wednesday, December 13, 2023 4:45 PM
> >>To: Kershner, David <david.kershner at intel.com>; intel-
> >>xe at lists.freedesktop.org; Ruhl, Michael J <michael.j.ruhl at intel.com>;
> >>Fleck, John <john.fleck at intel.com>; De Marchi, Lucas
> >><lucas.demarchi at intel.com>; Vivi, Rodrigo <rodrigo.vivi at intel.com>;
> >>Roper, Matthew D <matthew.d.roper at intel.com>
> >>Subject: [PATCH v3 0/3] Add support for XeLink device
> >>
> >>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.
> >>
> >>Changes from version 1:
> >>	- Fix kernel-doc error
> >>Changes from version 2:
> >>	- Fix up rebase conflicts
> >
> >For the series:
> >
> >Reviewed-by: Michael J. Ruhl <michael.j.ruhl at intel.com>
> 
> Hold on on merging this as it touches the uapi and we are in the final phase of
> uapi cleanup for upstream submission. We don't want last minute additions
> there.

Will do, do we know the time limit for uapi merge completed?

David Kershner

> 
> Lucas De Marchi