Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / c0a0758034c655a78f307588895e63a5d4615abd
commitc0a0758034c655a78f307588895e63a5d4615abd[log] [tgz]
authorAdriana Kobylak <anoo@us.ibm.com>Wed Oct 13 15:52:25 2021 +0000
committerShawn McCarney <shawnmm@us.ibm.com>Mon Nov 08 22:20:16 2021 +0000
treedf8759e59e199f767d712931d493189183ad6810
parent886574cd772be492212cd5a1fde8bc2de8dabf9b [diff]
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>
3 files changed
tree: df8759e59e199f767d712931d493189183ad6810
  1. cold-redundancy/
  2. example/
  3. org/
  4. phosphor-power-sequencer/
  5. phosphor-power-supply/
  6. phosphor-regulators/
  7. power-sequencer/
  8. power-supply/
  9. services/
  10. test/
  11. tools/
  12. .clang-format
  13. .gitignore
  14. .shellcheck
  15. argument.hpp
  16. device.hpp
  17. device_monitor.hpp
  18. elog-errors.hpp
  19. file_descriptor.hpp
  20. gpio.cpp
  21. gpio.hpp
  22. LICENSE
  23. MAINTAINERS
  24. meson.build
  25. meson_options.txt
  26. names_values.hpp
  27. OWNERS
  28. pmbus.cpp
  29. pmbus.hpp
  30. README.md
  31. types.hpp
  32. utility.cpp
  33. utility.hpp
README.md

Overview

This repository contains applications for configuring and monitoring devices that deliver power to the system.

  • cold-redundancy: Application that makes power supplies work in Cold Redundancy mode and rotates them at intervals.
  • phosphor-power-sequencer: Applications for configuring and monitoring power sequencer and related devices that support JSON-driven configuration.
  • phosphor-power-supply: Next generation power supply monitoring application.
  • phosphor-regulators: JSON-driven application that configures and monitors voltage regulators.
  • power-sequencer: A power sequencer monitoring application.
  • power-supply: Original power supply monitoring application.
  • tools/power-utils: Power supply utilities.

Build

To build all applications in this repository:

  meson build
  ninja -C build

To clean the repository and remove all build output:

  rm -rf build

You can specify meson options to customize the build process. For example, you can specify:

  • Which applications to build and install.
  • Application-specific configuration data, such as power sequencer type.
  • Whether to build tests.

Power Supply Monitor and Util JSON config

Several applications in this repository require a PSU JSON config to run. The JSON config file provides information for:

  • Where to access the pmbus attributes
  • Which attribute file in pmbus maps to which property and interface in D-Bus
  • Which kernel device directory is used on which PSU

There is an example psu.json to describe the necessary configurations.

  • inventoryPMBusAccessType defines the pmbus access type, which tells the service which sysfs type to use to read the attributes. The possible values are:
    • Base: The base dir, e.g. /sys/bus/i2c/devices/3-0069/
    • Hwmon: The hwmon dir, e.g. /sys/bus/i2c/devices/3-0069/hwmon/hwmonX/
    • Debug: The pmbus debug dir, e.g. /sys/kernel/debug/pmbus/hwmonX/
    • DeviceDebug: The device debug dir, e.g. '/sys/kernel/debug/./`
    • HwmonDeviceDebug: The hwmon device debug dir, e.g. /sys/kernel/debug/pmbus/hwmonX/cffps1/
  • fruConfigs defines the mapping between the attribute file and the FRU inventory interface and property. The configuration example below indicates that the service will read part_number attribute file from a directory specified by the above pmbus access type, and assign to PartNumber property in xyz.openbmc_project.Inventory.Decorator.Asset interface.
      "fruConfigs": [
    {
      "propertyName": "PartNumber",
      "fileName": "part_number",
      "interface": "xyz.openbmc_project.Inventory.Decorator.Asset"
    }
  ]
  • psuDevices defines the kernel device dir for each PSU in inventory. The configuration example below indicates that powersupply0's device is located in /sys/bus/i2c/devices/3-0069.
      "psuDevices": {
    "/xyz/openbmc_project/inventory/system/chassis/motherboard/powersupply0" : "/sys/bus/i2c/devices/3-0069",
  }