Searched hist:c567dc8d (Results 1 – 5 of 5) sorted by relevance
| /openbmc/openpower-occ-control/ |
| H A D | occ_command.cpp | c567dc8d Fri Apr 01 15:09:17 CDT 2022 Chris Cain <cjcain@us.ibm.com> Prevent termination on OCC open/read/write errors
Instead of creating an elog and terminating, the code will now retry on
a Open/Read/Write failure and if it continues to fail, it will return a
CommFailure to the caller. Then the caller of can determine how to
handle (reset PM complex or ignore).
Normally all communication errors with the OCC should trigger an OCC
reset.
Change-Id: Ibf272270156edae565231ca429f15e8fca2f15bc
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
|
| H A D | occ_command.hpp | c567dc8d Fri Apr 01 15:09:17 CDT 2022 Chris Cain <cjcain@us.ibm.com> Prevent termination on OCC open/read/write errors
Instead of creating an elog and terminating, the code will now retry on
a Open/Read/Write failure and if it continues to fail, it will return a
CommFailure to the caller. Then the caller of can determine how to
handle (reset PM complex or ignore).
Normally all communication errors with the OCC should trigger an OCC
reset.
Change-Id: Ibf272270156edae565231ca429f15e8fca2f15bc
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
|
| H A D | powermode.cpp | c567dc8d Fri Apr 01 15:09:17 CDT 2022 Chris Cain <cjcain@us.ibm.com> Prevent termination on OCC open/read/write errors
Instead of creating an elog and terminating, the code will now retry on
a Open/Read/Write failure and if it continues to fail, it will return a
CommFailure to the caller. Then the caller of can determine how to
handle (reset PM complex or ignore).
Normally all communication errors with the OCC should trigger an OCC
reset.
Change-Id: Ibf272270156edae565231ca429f15e8fca2f15bc
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
|
| H A D | occ_pass_through.cpp | c567dc8d Fri Apr 01 15:09:17 CDT 2022 Chris Cain <cjcain@us.ibm.com> Prevent termination on OCC open/read/write errors
Instead of creating an elog and terminating, the code will now retry on
a Open/Read/Write failure and if it continues to fail, it will return a
CommFailure to the caller. Then the caller of can determine how to
handle (reset PM complex or ignore).
Normally all communication errors with the OCC should trigger an OCC
reset.
Change-Id: Ibf272270156edae565231ca429f15e8fca2f15bc
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
|
| H A D | occ_status.cpp | c567dc8d Fri Apr 01 15:09:17 CDT 2022 Chris Cain <cjcain@us.ibm.com> Prevent termination on OCC open/read/write errors
Instead of creating an elog and terminating, the code will now retry on
a Open/Read/Write failure and if it continues to fail, it will return a
CommFailure to the caller. Then the caller of can determine how to
handle (reset PM complex or ignore).
Normally all communication errors with the OCC should trigger an OCC
reset.
Change-Id: Ibf272270156edae565231ca429f15e8fca2f15bc
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
|