Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 1c40f1c17c01a3f58da7c3fd367a9f3a55dbaa33
commit1c40f1c17c01a3f58da7c3fd367a9f3a55dbaa33[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Apr 08 19:32:43 2020 -0400
committerShawn McCarney <shawnmm@us.ibm.com>Wed Apr 29 10:08:10 2020 -0500
treeff7ff1fc40a706824093468627ff6c971674c118
parent01bc612007c0248745a90f857fb9f72ba1586407 [diff]
meson: add options for each application

None of our users use _all_ of phosphor-power - give them the ability to
configure in or out whatever applications they require.

Initially align options to how downstream distros (OpenBMC) are already
packaging our applications:

utils - general purpose utilities.
supply-monitor - the original power supply monitor.
supply-monitor-ng - the power supply monitor rewrite.
regulators - support for regulator config, control and monitoring.
sequencer-monitor - support for monitoring the ucd90160 power sequencer.
cold-redundancy - support for cold redundancy

Change-Id: Idac1860bb2648717d7c43b849757c5ddd6a23ab0
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: ff7ff1fc40a706824093468627ff6c971674c118
  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",
  }