On Thu, Jul 06, 2023 at 04:59:09PM -0500, richard.yu@xxxxxxx wrote: > From: Richard Yu <richard.yu@xxxxxxx> > > The HPE GXP vEHCI controller presents a four port EHCI compatible PCI > function to host software. Each vEHCI port is logically connected to a > corresponding set of virtual device registers. What makes the vEHCI controller virtual? Presenting a "PCI function" certainly seems to indicate it is a physical device, indeed, a PCI device. > > Signed-off-by: Richard Yu <richard.yu@xxxxxxx> > --- > drivers/usb/gadget/udc/Kconfig | 6 + > drivers/usb/gadget/udc/Makefile | 1 + > drivers/usb/gadget/udc/gxp-udc.c | 1401 ++++++++++++++++++++++++++++++ > 3 files changed, 1408 insertions(+) > create mode 100644 drivers/usb/gadget/udc/gxp-udc.c > > diff --git a/drivers/usb/gadget/udc/Kconfig b/drivers/usb/gadget/udc/Kconfig > index 83cae6bb12eb..c01eb2a2c7db 100644 > --- a/drivers/usb/gadget/udc/Kconfig > +++ b/drivers/usb/gadget/udc/Kconfig > @@ -461,6 +461,12 @@ config USB_ASPEED_UDC > dynamically linked module called "aspeed_udc" and force all > gadget drivers to also be dynamically linked. > > +config USB_GXP_UDC > + bool "GXP UDC Driver" > + depends on ARCH_HPE_GXP || COMPILE_TEST > + help > + Say "y" to add support for GXP UDC driver Now hang on a second. What sort of driver is this patch adding support for: a GXP vEHCI controller driver or a GXP UDC controller driver? The patch description says the first, but the code says the second. It sounds like this thing actually is a PCI device that appears to the OS as an actual EHCI controller, but with virtual (rather than physical) downstream ports, and it includes a virtual UDC for each port. As such, it requires a driver for the virtual UDCs, which is what this patch provides. (No new driver is needed for the EHCI controller part, since the kernel already has an EHCI driver.) Is that a correct description? And if it is, what is the purpose of this device? To act as a testing ground for gadget drivers? Alan Stern
