tree e32f5378b91b3992a99a60348836bb8d949240bb
parent c9b05736f43c9e16737a31140ff2b7a36373da81
author Adriana Kobylak <anoo@us.ibm.com> 1646235452 +0000
committer Shawn McCarney <shawnmm@us.ibm.com> 1648493078 +0000

psu-ng: Set the PowerSystemInputs status on Brownout condition

When a brownout condition is detected, set the PowerSystemInputs status
property to Fault to avoid an autorestart, reference design doc:
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/48015

Add a Before=xyz.openbmc_project.State.Chassis.service to the psu
monitor service file since the chassis service is the one that will be
reading the property.

Add additional data to the Blackout error log.

Tested: On simulation:

1. Clear brownout at runtime:
- At power on, inject a power fault to all PSUs to trigger a brownout
  and verify the CurrentPowerStatus is set to Fault:

Mar 20 19:49:14 p10bmc phosphor-log-manager[318]: Created PEL 0x5000000d
(BMC ID 13) with SRC 110000AC
Mar 20 19:49:14 p10bmc phosphor-power-control[307]:
callbackSetPowerSupplyError:
xyz.openbmc_project.State.Shutdown.Power.Error.Blackout

‣ Type=signal  Endian=l  Flags=1  Version=1 Cookie=94  Timestamp="Sun
2022-03-20 19:49:14.241856 UTC"
  Sender=:1.1296
Path=/xyz/openbmc_project/power/power_supplies/chassis0/psus
Interface=org.freedesktop.DBus.Properties  Member=PropertiesChanged
...
          STRING
"xyz.openbmc_project.State.Decorator.PowerSystemInputs";
...
                                  STRING
"xyz.openbmc_project.State.Decorator.PowerSystemInputs.Status.Fault";

- Additional data on the error log:

"User Data 1": {
    "Section Version": "1",
    "Sub-section type": "1",
    "Created by": "0x2000",
    "NOT_PRESENT_COUNT": "2",
    "VIN_FAULT_COUNT": "2",
    "_PID": "10244"
}

- Clear the brownout condition and verify the status is set to Good.

Change-Id: I29695b641fb81515680a478e872bac29a6de560a
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>