Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 32707088bf4eae60d0e16b4485768601a56d912c
commit32707088bf4eae60d0e16b4485768601a56d912c[log] [tgz]
authorMatthew Barth <msbarth@us.ibm.com>Mon Apr 13 13:59:04 2020 -0500
committerMatthew Barth <msbarth@us.ibm.com>Mon Apr 27 16:09:02 2020 -0500
tree0a6882ab48c406967b4e3a3fb66236f2c5307125
parentcd9ab087e6888796876df44e0fa998f1b5583877 [diff]
regs: Regulators control program

The regulators control program is used to control the mode in which the
phosphor-regulators application should run in. This is done by doing
dbus method calls into the phosphor-regulators service which changes the
mode in which the application runs.

Tested:
    Handles unsupported arguments and parameters
    Configure mode method called
    Enable monitoring mode method called
    Disable monitoring mode method called

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ia9c9b48469d39059d32518949faaa50c6a038236
2 files changed
tree: 0a6882ab48c406967b4e3a3fb66236f2c5307125
  1. cold-redundancy/
  2. example/
  3. org/
  4. phosphor-power-supply/
  5. phosphor-regulators/
  6. power-sequencer/
  7. power-supply/
  8. services/
  9. test/
  10. tools/
  11. .clang-format
  12. .gitignore
  13. argument.hpp
  14. device.hpp
  15. device_monitor.hpp
  16. elog-errors.hpp
  17. file.hpp
  18. gpio.cpp
  19. gpio.hpp
  20. LICENSE
  21. MAINTAINERS
  22. meson.build
  23. meson_options.txt
  24. names_values.hpp
  25. pmbus.cpp
  26. pmbus.hpp
  27. README.md
  28. types.hpp
  29. utility.cpp
  30. utility.hpp
README.md

Code for detecting and analyzing power faults on Witherspoon.

To Build

To build this package, do the following steps:

    1. meson build
    2. ninja -C build

To clean the repository again run `rm -rf build`.

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",
  }