scsi: cxlflash: Introduce object handle fop
authorUma Krishnan <ukrishn@linux.vnet.ibm.com>
Mon, 26 Mar 2018 16:34:35 +0000 (11:34 -0500)
committerMartin K. Petersen <martin.petersen@oracle.com>
Wed, 18 Apr 2018 23:32:50 +0000 (19:32 -0400)
commit402a55ea473a37b06eeae9abda00886bfd3bfe6d
treecec70dfe37a352d5dd279e90e69813ab14a26e41
parente117c3c731c26bae77b16707740876ede6f73a1b
scsi: cxlflash: Introduce object handle fop

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>
drivers/scsi/cxlflash/backend.h
drivers/scsi/cxlflash/cxl_hw.c
drivers/scsi/cxlflash/ocxl_hw.c