tree 7c17e4e7bd654a9654ebaf32fb985165b5bc799d
parent 9bc5f7681c26df8fbd6e01cd0ea15c8842a2c133
author Brandon Wyman <bjwyman@gmail.com> 1655312301 +0000
committer Shawn McCarney <shawnmm@us.ibm.com> 1658845679 +0000

psu-ng: PGOOD_DEGLITCH_LIMIT of five

Turns out that the (IBM) power supplies take up to around 3 seconds to
get the PGOOD# bit in STATUS_WORD set to the good (0) state after the
input power is within range. Adjust the de-glitch value to avoid logging
PGOOD errors for the power supplies, as they mostly ride through the
momentary drops in the input power.

Use PGOOD_DEGLITCH_LIMIT instead of DEGLITCH_LIMIT for the pgoodFault.

Tested:
    Rainier 2S4U
        1. Drop outlet power for 0.5 seconds, verify no 110015F1.
        2. Drop outlet power for 1 second, verify no 110015F1.
        3. Drop outlet power for 1.5 seconds, verify no 110015F1.
    Rainier 2S2U
        1. Drop outlet power for 1 second, verify no 110015F1.
        2. Drop outlet power for 5 seconds, verify 110015F0 (VIN_UV) IS logged.
        3. Drop outlet power for 1.5 seconds, verify no 110015F1.
    Everest (powersupply0 unplugged, powersupply3 missing)
        1. Drop outlet power for 0.5 seconds, verify no 110015F1.
        2. Drop outlet power for 1 second, verify no 110015F1.
        3. Drop outlet power for 1.5 seconds, verify no 110015F1.
        4. Drop outlet power for 3 seconds, verify 110015F0 IS logged.
        5. Drop all outlet power for 5 seconds, verify 110000AC.

Change-Id: I6ba12209e6c84548fec036101ca02d857ed900f6
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>