Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 3d1ebcb4d29015a3ca99c7037b5476aa8ae4b5fe
commit3d1ebcb4d29015a3ca99c7037b5476aa8ae4b5fe[log] [tgz]
authorLei YU <mine260309@gmail.com>Mon Jan 06 10:50:32 2020 +0800
committerLei YU <mine260309@gmail.com>Mon Jan 20 03:05:32 2020 +0000
tree68ccb47f70535fc8ec6f15f83c4d8c5f07500fe8
parent5cc0128068ef5fcfd49e99099a5d6339cd69f272 [diff]
power-supply: Remove version interface

In power supply monitor, a version interface is created in the PSU
object in inventory (/xyz/openbmc_project/inventory).

With PSU code manager implemented in OpenBMC, the version object is
created under software (/xyz/openbmc_project/software), so the version
interface in inventory is not necessary anymore.

Tested: Verify the version and purpose do not exist anymore in
        /xyz/openbmc_project/inventory/system/chassis/motherboard/powersupply[0|1]
        on Witherspoon, after factory reset.

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