diff options
| author | Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com> | 2018-09-07 10:31:25 +0530 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.ibm.com> | 2018-09-17 21:39:02 -0500 |
| commit | 1317448ddd1a872e93a6f421ba5cd5d9b3b6ea7a (patch) | |
| tree | 3c74d430ea7525002c9a98483c4af4f0e7090aac /hw/p8-i2c.c | |
| parent | 5f728c53d42c664234b45a33218ba522a6e8f216 (diff) | |
| download | skiboot-1317448ddd1a872e93a6f421ba5cd5d9b3b6ea7a.zip skiboot-1317448ddd1a872e93a6f421ba5cd5d9b3b6ea7a.tar.gz skiboot-1317448ddd1a872e93a6f421ba5cd5d9b3b6ea7a.tar.bz2 | |
opal/hmi: Ignore debug trigger inject core FIR.
Core FIR[60] is a side effect of the work around for the CI Vector Load
issue in DD2.1. Usually this gets delivered as HMI with HMER[17] where
Linux already ignores it. But it looks like in some cases we may happen
to see CORE_FIR[60] while we are already in Malfunction Alert HMI
(HMER[0]) due to other reasons e.g. CAPI recovery or NPU xstop. If that
happens then just ignore it instead of crashing kernel as not recoverable.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Reviewed-by: Vaibhav Jain <vaibhav@linux.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to 'hw/p8-i2c.c')
0 files changed, 0 insertions, 0 deletions