docs/designs/psu-monitoring.md

7 Created: 2019-06-17
16 validate configurations, report invalid configurations, detect and report
22 The OpenBMC project currently has a [witherspoon-pfault-analysis][1] repository
38 1. The power supply application must detect, isolate, and report individual
47    moved from the `phosphor-dbus-monitor` to this application, depending on if
55 7. The power supply application must allow power supply hot-plug and concurrent
59 9. The power supply application must be able to detect how many power supplies
65     the application updating properties for a Minimum Ship Level ([MSL][3])
72     only known to be created and updated by the [ibm-cffps][4] device driver).
84 [phosphor-power][6] repository. The application would be written in C++17.
88 file. This file would contain information such as the D-Bus object name(s),
93 The power supply application would then detect which system type it is running
112 considered, essentially similar to the [psu-monitor][5] from the
113 [witherspoon-pfault-analysis][1] repository. This design was avoided due to:
115 - Complexity of the various valid and invalid configuration combinations.
116 - Power line disturbance communication.
117 - Timing/serialization concerns with power supply communication.
136 - Configuration not listed as valid results in appropriate behavior.
137 - Application detects and logs faults for power supply faults including input
140 - Power supply VPD data reported for present power supplies.
141 - Power supply removal and insertion, on a system supporting concurrent
143 - System operates through power supply faults and power line disturbances as
149 [1]: https://github.com/openbmc/witherspoon-pfault-analysis
152 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Control/R…
154   https://github.com/openbmc/linux/blob/dev-5.3/drivers/hwmon/pmbus/ibm-cffps.c
156   https://github.com/openbmc/witherspoon-pfault-analysis/tree/master/power-supply
157 [6]: https://github.com/openbmc/phosphor-power/