Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 575ed139220d7a694893f8b1a1e2d4c3b69317fe
commit575ed139220d7a694893f8b1a1e2d4c3b69317fe[log] [tgz]
authorLei YU <mine260309@gmail.com>Tue Oct 29 17:22:16 2019 +0800
committerShawn McCarney <shawnmm@us.ibm.com>Wed Dec 04 16:13:41 2019 +0000
tree2d43f255259ccf26b11187f9c9e02b2548caaa96
parent6d5977375f5ca0a8676c6337e465bf7c92f3a765 [diff]
power-utils: Initially add isReadyToUpdate

Initially add isReadyToUpdate() that checks the pre-condition for PSU
update.
For now it only checks the power state and return false if power is on.

When it is not ready to update, there is no need to unbind/bind the
driver, so move the unbind/bind calls into doUpdate() from ctor/dtor.

Tested: Verify it returns and logs "PSU not ready to update" when power
        is on, and continues the update when power is off.

Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: I1cbb454baf735ceb3de883a7317753d46485696f
2 files changed
tree: 2d43f255259ccf26b11187f9c9e02b2548caaa96
  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",
  }