diff options
| author | Russell Currey <ruscur@russell.cc> | 2016-07-20 19:09:20 +0530 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2016-07-21 11:51:21 +1000 |
| commit | 4ae024ed5b9b5e475783c9f930183506ab32a0d9 (patch) | |
| tree | 93019881b9028df932a43674250d0fb91fcfb814 /doc | |
| parent | a7ba9f22c48a7051a71301bf19b5b358d3fc4ceb (diff) | |
| download | skiboot-4ae024ed5b9b5e475783c9f930183506ab32a0d9.zip skiboot-4ae024ed5b9b5e475783c9f930183506ab32a0d9.tar.gz skiboot-4ae024ed5b9b5e475783c9f930183506ab32a0d9.tar.bz2 | |
xscom: Return OPAL_WRONG_STATE on XSCOM ops if CPU is asleep
xscom_read and xscom_write return OPAL_SUCCESS if they worked, and
OPAL_HARDWARE if they didn't. This doesn't provide information about why
the operation failed, such as if the CPU happens to be asleep.
This is specifically useful in error scanning, so if every CPU is being
scanned for errors, sleeping CPUs likely aren't the cause of failures.
So, return OPAL_WRONG_STATE in xscom_read and xscom_write if the CPU is
sleeping.
Signed-off-by: Russell Currey <ruscur@russell.cc>
Reviewed-by: Alistair Popple <alistair@popple.id.au>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
(cherry picked from commit 9c2d82394fd2303847cac4a665dee62556ca528a)
Signed-off-by: Vipin K Parashar <vipin@linux.vnet.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/opal-api/opal-xscom-read-write-65-66.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/opal-api/opal-xscom-read-write-65-66.txt b/doc/opal-api/opal-xscom-read-write-65-66.txt index 92916df..4ed0134 100644 --- a/doc/opal-api/opal-xscom-read-write-65-66.txt +++ b/doc/opal-api/opal-xscom-read-write-65-66.txt @@ -10,3 +10,8 @@ each takes three parameters: int xscom_read(uint32_t partid, uint64_t pcb_addr, uint64_t *val) int xscom_write(uint32_t partid, uint64_t pcb_addr, uint64_t val) + +Returns: + OPAL_SUCCESS + OPAL_HARDWARE if operation failed + OPAL_WRONG_STATE if CPU is asleep |