linux.git/include/misc/ocxl.h, branch v5.3.2

ocxl: Update for AFU descriptor template version 1.1

2019-07-10T03:20:44+00:00

The OpenCAPI discovery and configuration specification has been
updated and introduces version 1.1 of the AFU descriptor template,
with new fields to better define the memory layout of an OpenCAPI
adapter.

The ocxl driver doesn't do much yet to support LPC memory but as we
start seeing (non-LPC) AFU images using the new template, this patch
updates the config space parsing code to avoid spitting a warning.

Signed-off-by: Alastair D'Silva 
Signed-off-by: Frederic Barrat 
Reviewed-by: Christophe Lombard 
Acked-by: Andrew Donnellan 
Signed-off-by: Michael Ellerman 
Link: https://lore.kernel.org/r/20190605111545.19762-1-fbarrat@linux.ibm.com

ocxl: Provide global MMIO accessors for external drivers

2019-05-02T16:55:02+00:00

External drivers that communicate via OpenCAPI will need to make
MMIO calls to interact with the devices.

Signed-off-by: Alastair D'Silva 
Reviewed-by: Greg Kurz 
Acked-by: Frederic Barrat 
Signed-off-by: Michael Ellerman

ocxl: move event_fd handling to frontend

2019-05-02T16:55:02+00:00

Event_fd is only used in the driver frontend, so it does not
need to exist in the backend code. Relocate it to the frontend
and provide an opaque mechanism for consumers instead.

Signed-off-by: Alastair D'Silva 
Acked-by: Frederic Barrat 
Signed-off-by: Michael Ellerman

ocxl: Allow external drivers to use OpenCAPI contexts

2019-05-02T16:55:02+00:00

Most OpenCAPI operations require a valid context, so
exposing these functions to external drivers is necessary.

Signed-off-by: Alastair D'Silva 
Reviewed-by: Greg Kurz 
Acked-by: Frederic Barrat 
Signed-off-by: Michael Ellerman

ocxl: Create a clear delineation between ocxl backend & frontend

2019-05-02T16:55:01+00:00

The OCXL driver contains both frontend code for interacting with userspace,
as well as backend code for interacting with the hardware.

This patch separates the backend code from the frontend so that it can be
used by other device drivers that communicate via OpenCAPI.

Relocate dev, cdev & sysfs files to the frontend code to allow external
drivers to maintain their own devices.

Reference counting on the device in the backend is replaced with kref
counting.

Move file & sysfs layer initialisation from core.c (backend) to
pci.c (frontend).

Create an ocxl_function oriented interface for initing devices &
enumerating AFUs.

Signed-off-by: Alastair D'Silva 
Acked-by: Frederic Barrat 
Signed-off-by: Michael Ellerman

ocxl: Remove some unused exported symbols

2019-05-02T16:55:01+00:00

Remove some unused exported symbols.

Signed-off-by: Alastair D'Silva 
Reviewed-by: Greg Kurz 
Acked-by: Frederic Barrat 
Acked-by: Andrew Donnellan 
Signed-off-by: Michael Ellerman

ocxl: Remove superfluous 'extern' from headers

2019-05-02T16:55:01+00:00

The 'extern' keyword adds no value here.

Signed-off-by: Alastair D'Silva 
Reviewed-by: Greg Kurz 
Acked-by: Frederic Barrat 
Acked-by: Andrew Donnellan 
Signed-off-by: Michael Ellerman

ocxl: Expose the thread_id needed for wait on POWER9

2018-06-03T10:40:32+00:00

In order to successfully issue as_notify, an AFU needs to know the TID
to notify, which in turn means that this information should be
available in userspace so it can be communicated to the AFU.

Signed-off-by: Alastair D'Silva 
Acked-by: Andrew Donnellan 
Signed-off-by: Michael Ellerman

ocxl: Add a kernel API for other opencapi drivers

2018-01-24T00:42:59+00:00

Some of the functions done by the generic driver should also be needed
by other opencapi drivers: attaching a context to an adapter,
translation fault handling, AFU interrupt allocation...

So to avoid code duplication, the driver provides a kernel API that
other drivers can use, similar to calling a in-kernel library.

It is still a bit theoretical, for lack of real hardware, and will
likely need adjustements down the road. But we used the cxlflash
driver as a guinea pig.

Signed-off-by: Frederic Barrat 
Signed-off-by: Michael Ellerman