Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 9ab6d7501fb457020d50fc41caad2b0eb8dcf08b
commit9ab6d7501fb457020d50fc41caad2b0eb8dcf08b[log] [tgz]
authorLei YU <mine260309@gmail.com>Mon Oct 28 17:03:20 2019 +0800
committerLei YU <mine260309@gmail.com>Tue Nov 05 03:02:45 2019 +0000
treee963aaa89827c0afc1c3c1cf409b5154cd54267e
parentd19df255c75ed3df986b2e41ca2bc4a6ba88941c [diff]
power-utils: Initially add Updater class

The Updater class is used to do PSU code update, initially add it that
does unbind/bind driver and set PSU present to false/true during the
update.

Tested: Manually verify on Witherspoon that the driver is unbind/bind,
        and the PSU present property is set to false/true during the PSU
        update:
          psutils --update \
          /xyz/openbmc_project/inventory/system/chassis/motherboard/powersupply0 \
          /tmp/images/xxxxxxxx

Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: Ic0a9df7687303caeb9a7f21ba00dc33ee76482db
4 files changed
tree: e963aaa89827c0afc1c3c1cf409b5154cd54267e
  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. utility.cpp
  27. 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",
  }