tree 1e6c511c32e55f708ae06ee02bc9cbaad78493f9
parent 5ba5a8ec2fe3fdfe51e7817199337bebb759627b
author Yikai Tsai <yikai.tsai.wiwynn@gmail.com> 1724132943 +0800
committer Patrick Williams <patrick@stwcx.xyz> 1724240336 +0000

meta-facebook: yosemite4: Fan board eFuse fault event

Summary:
The system shall register an event in response to fan board eFuse fault.
BMC is triggered by INT_FANBOARD0_IOEXP_N or INT_FANBOARD1_IOEXP_N to
identify which fan board has eFuse fault.
Then, BMC reads relevant fan board IOE to check affected eFuse.

Test Plan:
Pull FLT_EFUSE0_N low to make INT_FANBOARD0_IOEXP_N be low.

Testing:
Take fan board 0 and eFuse 0 for example.

1. Check fan board 0 IOE init status
root@bmc:~# i2ctransfer -f -y 30 w1@0x22 0 r1
0xff

2. Pull FLT_EFUSE0_N low and check fan board 0 IOE init status
root@bmc:~# i2ctransfer -f -y 30 w1@0x22 0 r1
0xfb

3. Check event log
root@bmc:~# mfg-tool log-display
...
    "2": {
        "additional_data": [
            "FAULT=eFuse0"
        ],
        "event_id": "",
        "message": "Fan board 0 eFuse fault",
        "resolution": "",
        "resolved": false,
        "severity": "xyz.openbmc_project.Logging.Entry.Level.Error",
        "timestamp": "2024-02-27T17:31:55.420000000Z",
        "updated_timestamp": "2024-02-27T17:31:55.420000000Z"
    }

Change-Id: Idb1a6a767b1e412931d229eb9cfaac7624fdec0a
Signed-off-by: Yikai Tsai <yikai.tsai.wiwynn@gmail.com>