tree a76a102cc5ae0046b6527dc02325c2cd5e20e21e
parent 110b284175c5ccb6e740b64b2b8af814678510d8
author Matt Spinler <spinler@us.ibm.com> 1503347754 -0500
committer Patrick Williams <patrick@stwcx.xyz> 1505845600 +0000

Fill in PGOOD fault checking code

Fill in the code to check for a PGOOD fault.  This is where
the power sequencer device detects that one of its child devices
lost PGOOD.  A separate error log will be created for each input
that has a fault.  Each input will only have an error logged against
it once for the lifetime of the object.

Errors are detected by reading the real time status of the PGOOD input,
which is exposed as a GPIO by the device driver.

Ideally we would be able to use a summary bit in the status_word
register to see if there is an error before doing any GPIO reads,
but as the device drivers sends a clear faults every time we read
that register, and the GPI fault bits are edge triggered in the
mfr_status register that feeds status_word, we would never detect
any failures.  If this was ever fixed in the core PMBus device
driver code, we could add this functionality in and save some
CPU cycles.

Change-Id: I5000f2ebc2b22dcca946154afd2405b29734ccaf
Signed-off-by: Matt Spinler <spinler@us.ibm.com>