ocxl: Driver code for 'generic' opencapi devices
Add an ocxl driver to handle generic opencapi devices. Of course, it's not meant to be the only opencapi driver, any device is free to implement its own. But if a host application only needs basic services like attaching to an opencapi adapter, have translation faults handled or allocate AFU interrupts, it should suffice. The AFU config space must follow the opencapi specification and use the expected vendor/device ID to be seen by the generic driver. The driver exposes the device AFUs as a char device in /dev/ocxl/ Note that the driver currently doesn't handle memory attached to the opencapi device. Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com> Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com> Signed-off-by: Alastair D'Silva <alastair@d-silva.org> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Showing
drivers/misc/ocxl/config.c
0 → 100644
drivers/misc/ocxl/context.c
0 → 100644
drivers/misc/ocxl/file.c
0 → 100644
drivers/misc/ocxl/link.c
0 → 100644
drivers/misc/ocxl/main.c
0 → 100644
drivers/misc/ocxl/pasid.c
0 → 100644
drivers/misc/ocxl/pci.c
0 → 100644
drivers/misc/ocxl/sysfs.c
0 → 100644
include/uapi/misc/ocxl.h
0 → 100644
Please register or sign in to comment