diff options
author | Mike Jones <mjjones@us.ibm.com> | 2012-03-22 08:40:50 -0500 |
---|---|---|
committer | A. Patrick Williams III <iawillia@us.ibm.com> | 2012-03-23 15:33:50 -0500 |
commit | 2b799ae5c3683fa7753bfe9527c517000c91a1d4 (patch) | |
tree | 631fdb01a4d01e9d5c7229f1f1819244cdf8dabb /src/include/usr/mbox | |
parent | b519667966e373477febd4b3f1c84ffa1aa5e6a7 (diff) | |
download | talos-hostboot-2b799ae5c3683fa7753bfe9527c517000c91a1d4.tar.gz talos-hostboot-2b799ae5c3683fa7753bfe9527c517000c91a1d4.zip |
HWPF: Infrastructure to allow HWPs to look for specific PLAT errors
Currently when PLAT firmware (e.g. FSP, Hostboot, Cronus) attaches
an error log to a fapi::ReturnCode, the ReturnCode value is
FAPI_RC_PLAT_ERR_SEE_DATA, all a HWP receiving the ReturnCode knows
is that there is a PLAT error and it cannot look at the data (it is
PLAT specific). There will be future scenarios where HWPs need to
look for specific errors code from PLAT. The example given by Joe
McGill is ADU_LOCKED, a HWP may want to retry a SCOM operation if
the error is ADU_LOCKED. The way to do this will be to define a
PLAT return code value in fapiReturnCodes.H called
FAPI_RC_PLAT_ADU_ERR. PLAT code would set this special value and
attach its error log. Then HWP code can look for this special
value. This change is simply to allow PLAT code to specify the
return code value when attaching an error log to the ReturnCode.
Change-Id: I6bc3f0b4d3350cc3eed52fa947a5bf4a885095a5
RTC: 37970
Reviewed-on: http://gfw160.austin.ibm.com:8080/gerrit/785
Tested-by: Jenkins Server
Reviewed-by: Brian H. Horton <brianh@linux.ibm.com>
Reviewed-by: A. Patrick Williams III <iawillia@us.ibm.com>
Diffstat (limited to 'src/include/usr/mbox')
0 files changed, 0 insertions, 0 deletions