Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / c12c53b985b9ac12c3c83df47371e7c2c70ae21b
commitc12c53b985b9ac12c3c83df47371e7c2c70ae21b[log] [tgz]
authorChanh Nguyen <chanh@os.amperecomputing.com>Tue Apr 06 17:24:47 2021 +0700
committerShawn McCarney <shawnmm@us.ibm.com>Wed Apr 07 14:37:19 2021 +0000
tree00d2c52bb3351a94e185ba50c484c53dbbe95cfc
parent1553cd9a91df1d4cd0d1ba2feb53ba63004d3fdd [diff]
psu-ng: Change the IBM_VPD checking condition

By default, the IBM_VPD will be defined as 0 (False).
We used the "#ifdef IBM_VPD" to check the define IBM_VPD,
it's not correct completely. The source code of IBM VPD
always runs in both TRUE or FALSE.

Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
Change-Id: I7e6e9c5c2c62de3a1b7f52d2be1caf6b44f0a2f4
2 files changed
tree: 00d2c52bb3351a94e185ba50c484c53dbbe95cfc
  1. cold-redundancy/
  2. example/
  3. org/
  4. phosphor-power-sequencer/
  5. phosphor-power-supply/
  6. phosphor-regulators/
  7. power-sequencer/
  8. power-supply/
  9. services/
  10. test/
  11. tools/
  12. .clang-format
  13. .gitignore
  14. argument.hpp
  15. device.hpp
  16. device_monitor.hpp
  17. elog-errors.hpp
  18. file_descriptor.hpp
  19. gpio.cpp
  20. gpio.hpp
  21. LICENSE
  22. MAINTAINERS
  23. meson.build
  24. meson_options.txt
  25. names_values.hpp
  26. pmbus.cpp
  27. pmbus.hpp
  28. README.md
  29. types.hpp
  30. utility.cpp
  31. utility.hpp
README.md

Overview

This repository contains applications for configuring and monitoring devices that deliver power to the system.

  • cold-redundancy: Application that makes power supplies work in Cold Redundancy mode and rotates them at intervals.
  • phosphor-power-sequencer: Applications for configuring and monitoring power sequencer and related devices that support JSON-driven configuration.
  • phosphor-power-supply: Next generation power supply monitoring application.
  • phosphor-regulators: JSON-driven application that configures and monitors voltage regulators.
  • power-sequencer: A power sequencer monitoring application.
  • power-supply: Original power supply monitoring application.
  • tools/power-utils: Power supply utilities.

Build

To build all applications in this repository:

  meson build
  ninja -C build

To clean the repository and remove all build output:

  rm -rf build

You can specify meson options to customize the build process. For example, you can specify:

  • Which applications to build and install.
  • Application-specific configuration data, such as power sequencer type.
  • Whether to build tests.

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",
  }