tree a8cbabb257174cfa8d26be72bfb68d9d4b4bc8d8
parent de0fd44f76c7cd1ae63ec39e708b352a3a7ab0a9
author Jay Meyer <jaymeyer@us.ibm.com> 1606768881 -0600
committer Shawn McCarney <shawnmm@us.ibm.com> 1613504838 +0000

Capture PSU STATUS_MFR_SPECIFIC during analysis

If there is a fault indicated in STATUS_WORD, add the
STATUS_MFR_SPECIFIC value to the error log additional data.
For additional diagnostic information, include the MFR status
for all log entries when status word is nonzero.
Change the journal entry for MFR fault to an error type,
suggested in code review.

Tested: Test by setting the bit in the PMBus status word in simulation
        for MFR and a nonzero value in STATUS_MFR_SPECIFIC.
        The chassis is on during this test.
        This change also adds the MFR status in journal entries.
        The journal contains an entry like this for the MFR fault:
        MFR fault: status word = 0x01 MFR fault =  0x1
        Other journal entries:
        VIN_UV fault: status word = 0x08, MFR fault = 0x1
        INPUT fault: status word = 0x02, MFR fault = 0x1
        Note: definitions for INPUT_FAULT_WARN and MFR_SPECIFIC_FAULT
        were changed for testing purposes because the simulator could
        not set the upper bits of the status word.

Signed-off-by: Jay Meyer <jaymeyer@us.ibm.com>
Change-Id: Ib63ca6581c72f640aba01a95c6fe02b26ac8c1ee