Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 8122eee25eec5296f2ccb184b2ec8e050f43c808
commit8122eee25eec5296f2ccb184b2ec8e050f43c808[log] [tgz]
authorShawn McCarney <shawnmm@us.ibm.com>Tue Nov 12 16:54:27 2019 -0600
committerShawn McCarney <shawnmm@us.ibm.com>Tue Nov 12 16:54:27 2019 -0600
treeb2baca4aeeb5991dc85d424b23fe6452423b9a8e
parent2134ca66f2e6deb318382579f1cf5a402f7821df [diff]
Only build regulator tests when option enabled

Currently the regulator tests are always built.  This causes problems in
the Witherspoon SDK because it seems to contain an older, incompatible
version of gmock.

Modified the regulators meson file to only build the tests if the meson
'tests' option is enabled.

Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
Change-Id: I5bfe6ee22487085d37832e4b7b0d9f63c8751c0a
1 file changed
tree: b2baca4aeeb5991dc85d424b23fe6452423b9a8e
  1. example/
  2. org/
  3. phosphor-regulators/
  4. power-sequencer/
  5. power-supply/
  6. services/
  7. test/
  8. tools/
  9. .clang-format
  10. .gitignore
  11. argument.hpp
  12. device.hpp
  13. device_monitor.hpp
  14. elog-errors.hpp
  15. file.hpp
  16. gpio.cpp
  17. gpio.hpp
  18. LICENSE
  19. MAINTAINERS
  20. meson.build
  21. meson_options.txt
  22. names_values.hpp
  23. pmbus.cpp
  24. pmbus.hpp
  25. README.md
  26. types.hpp
  27. utility.cpp
  28. 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",
  }