Message ID | 20181031073213.14359-1-andrew.donnellan@au1.ibm.com |
---|---|
State | Superseded |
Headers | show |
Series | opal-api: Reserve 2 OPAL API calls for future OpenCAPI LPC use | expand |
Context | Check | Description |
---|---|---|
snowpatch_ozlabs/apply_patch | warning | master/apply_patch Patch failed to apply |
snowpatch_ozlabs/apply_patch | fail | Failed to apply to any branch |
diff --git a/include/opal-api.h b/include/opal-api.h index c24838d24e63..c793ca432782 100644 --- a/include/opal-api.h +++ b/include/opal-api.h @@ -227,7 +227,9 @@ #define OPAL_NPU_SET_RELAXED_ORDER 168 #define OPAL_NPU_GET_RELAXED_ORDER 169 #define OPAL_CLEAR_CACHE 170 -#define OPAL_LAST 170 +#define OPAL_NPU_RESERVED1 171 +#define OPAL_NPU_RESERVED2 172 +#define OPAL_LAST 172 #define QUIESCE_HOLD 1 /* Spin all calls at entry */ #define QUIESCE_REJECT 2 /* Fail all calls with OPAL_BUSY */
OpenCAPI Lowest Point of Coherency (LPC) memory is going to require some extra OPAL calls to set up NPU BARs. These calls will most likely be called OPAL_NPU_LPC_ALLOC and OPAL_NPU_LPC_RELEASE, we're not quite ready to upstream that code yet though. Reserve 171 and 172 for this purpose. Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com> --- This applies on top of Rashmica's patch https://patchwork.ozlabs.org/patch/990064/ Alastair: rashmica's patch means we'll need to increment the call numbers in our internal branch again unfortunately --- include/opal-api.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)