Searched hist:c0a0758034c655a78f307588895e63a5d4615abd (Results 1 – 3 of 3) sorted by relevance
/openbmc/phosphor-power/phosphor-power-supply/ |
H A D | util.cpp | diff c0a0758034c655a78f307588895e63a5d4615abd Wed Oct 13 10:52:25 CDT 2021 Adriana Kobylak <anoo@us.ibm.com> psu-ng: Set the power-config-full-load GPIO
The power-config-full-load GPIO is an optional GPIO that communicates to the HW the number of expected number of working PSUs. Reference: https://github.com/openbmc/docs/commit/2cbf57a8a0bb8d95b0e19b7fc27c4f95cbd8609a
If the system implements this GPIO, set it to the appropriate value when the psu monitor app starts, and every time the system powers on in case the number of PSUs was changed when the system was powered off.
In the GPIOReader constructor, move the error message from a journal log to the exception, otherwise this journal log will show up on all systems that do not implement this GPIO.
Tested:
Verified the correct value was set by reading the GPIO after writing by calling line.get_value() during testing.
Verified the GPIOReader only displays the error message when a GPIO does not exist and the exception is not caught, no error messages are displayed for a missing power-config-full-load GPIO: Oct 14 20:54:27 p10bmc phosphor-psu-monitor[1152]: Failed to find line: Line does not exist: test-gpio Oct 14 20:54:27 p10bmc systemd[1]: phosphor-psu-monitor.service: Main process exited, code=exited, status=254/n/a
Change-Id: Ifdcd9f552c28cec860b9b65a1133e179683fb0db Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
H A D | psu_manager.hpp | diff c0a0758034c655a78f307588895e63a5d4615abd Wed Oct 13 10:52:25 CDT 2021 Adriana Kobylak <anoo@us.ibm.com> psu-ng: Set the power-config-full-load GPIO
The power-config-full-load GPIO is an optional GPIO that communicates to the HW the number of expected number of working PSUs. Reference: https://github.com/openbmc/docs/commit/2cbf57a8a0bb8d95b0e19b7fc27c4f95cbd8609a
If the system implements this GPIO, set it to the appropriate value when the psu monitor app starts, and every time the system powers on in case the number of PSUs was changed when the system was powered off.
In the GPIOReader constructor, move the error message from a journal log to the exception, otherwise this journal log will show up on all systems that do not implement this GPIO.
Tested:
Verified the correct value was set by reading the GPIO after writing by calling line.get_value() during testing.
Verified the GPIOReader only displays the error message when a GPIO does not exist and the exception is not caught, no error messages are displayed for a missing power-config-full-load GPIO: Oct 14 20:54:27 p10bmc phosphor-psu-monitor[1152]: Failed to find line: Line does not exist: test-gpio Oct 14 20:54:27 p10bmc systemd[1]: phosphor-psu-monitor.service: Main process exited, code=exited, status=254/n/a
Change-Id: Ifdcd9f552c28cec860b9b65a1133e179683fb0db Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
H A D | psu_manager.cpp | diff c0a0758034c655a78f307588895e63a5d4615abd Wed Oct 13 10:52:25 CDT 2021 Adriana Kobylak <anoo@us.ibm.com> psu-ng: Set the power-config-full-load GPIO
The power-config-full-load GPIO is an optional GPIO that communicates to the HW the number of expected number of working PSUs. Reference: https://github.com/openbmc/docs/commit/2cbf57a8a0bb8d95b0e19b7fc27c4f95cbd8609a
If the system implements this GPIO, set it to the appropriate value when the psu monitor app starts, and every time the system powers on in case the number of PSUs was changed when the system was powered off.
In the GPIOReader constructor, move the error message from a journal log to the exception, otherwise this journal log will show up on all systems that do not implement this GPIO.
Tested:
Verified the correct value was set by reading the GPIO after writing by calling line.get_value() during testing.
Verified the GPIOReader only displays the error message when a GPIO does not exist and the exception is not caught, no error messages are displayed for a missing power-config-full-load GPIO: Oct 14 20:54:27 p10bmc phosphor-psu-monitor[1152]: Failed to find line: Line does not exist: test-gpio Oct 14 20:54:27 p10bmc systemd[1]: phosphor-psu-monitor.service: Main process exited, code=exited, status=254/n/a
Change-Id: Ifdcd9f552c28cec860b9b65a1133e179683fb0db Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|