scsi: cxlflash: Introduce object handle fop

Browse source

OCXL requires that AFUs use an opaque object handle to represent an AFU
interrupt. The specification does not provide a common means to communicate
the object handle to the AFU - each AFU must define this within the AFU
specification. To support this model, the object handle must be passed back to
the core driver as it manages the AFU specification (SISLite) for cxlflash.
Note that for Power systems, the object handle is the effective address of the
trigger page.

Signed-off-by: Uma Krishnan <ukrishn@linux.vnet.ibm.com>
Acked-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

...

This commit is contained in:

Uma Krishnan 2018-03-26 11:34:35 -05:00 • committed by Martin K. Petersen

parent e117c3c731

commit 402a55ea47

3 changed files with 26 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

drivers/scsi/cxlflash/backend.h

View file

7

drivers/scsi/cxlflash/cxl_hw.c

View file

18

drivers/scsi/cxlflash/ocxl_hw.c

View file