Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 1efdd62d297e0b27aa91b8f67a5b3b61e8f6cfa8
commit1efdd62d297e0b27aa91b8f67a5b3b61e8f6cfa8[log] [tgz]
authorMatthew Barth <msbarth@us.ibm.com>Fri Dec 20 14:16:31 2019 -0600
committerShawn McCarney <shawnmm@us.ibm.com>Fri Feb 21 15:09:03 2020 +0000
tree3fa5b76e404de6323e1f2831d8a32110d75276de
parentb3e48bca920006d5543549d547ebd284c7b3b124 [diff]
regulators: Add/install base service

Create a service file to start the phosphor-regulators binary that will
be linked to the multi-user target so that its started at BMC standby.
Add this service file to be installed within the systemd services
directory(`/lib/systemd/system/`).

Change https://gerrit.openbmc-project.xyz/27972 installs the binary

Tested:
    Service file installed in /lib/systemd/system/
    Linked to multi-user target in recipe and it started at BMC standby

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I5ef1485569ada2737e0e8d5ce11965c4eff0eb45
2 files changed
tree: 3fa5b76e404de6323e1f2831d8a32110d75276de
  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",
  }