Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 3a492527fd18be317e257a58c772c2fb7775376c
commit3a492527fd18be317e257a58c772c2fb7775376c[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Thu Nov 30 13:30:51 2023 -0600
committerShawn McCarney <shawnmm@us.ibm.com>Mon Dec 11 15:56:01 2023 +0000
tree76b036a991fc631c8fabc468916c936297ec2527
parentd694d8fcb0b15055a3e14567db975cc625dbe60c [diff]
power-supply: don't fail if synch gpio not found

Working on a new system, aptly named system1, I hit issues utilizing the
psu monitor on power on where it was failing and putting the BMC state
into Quiesced.

The reason was that the power-ffs-sync-history GPIO is not defined in
the device tree for system1. The power supply details are still being
worked but they are going to look a lot like the p10bmc supplies so
would like to utilize the psu-monitoring features. With this change I
confirmed that the system1 simulation model powers on and everything
looks good with the d-bus objects for the power supplies.

If the current behavior is desired, then we could look into a meson
config option to define whether the power synch function is wanted.

Tested:
- Confirmed system1 chassis poweron works without psu-monitor service
  failing

Change-Id: I3c8f50c6ae3c4ca150762e3828ab8a1935f7773f
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: 76b036a991fc631c8fabc468916c936297ec2527
  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. subprojects/
  11. test/
  12. tools/
  13. .clang-format
  14. .gitignore
  15. .shellcheck
  16. device.hpp
  17. device_monitor.hpp
  18. elog-errors.hpp
  19. file_descriptor.hpp
  20. gpio.cpp
  21. gpio.hpp
  22. LICENSE
  23. meson.build
  24. meson.options
  25. names_values.hpp
  26. OWNERS
  27. pmbus.cpp
  28. pmbus.hpp
  29. README.md
  30. types.hpp
  31. utility.cpp
  32. 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 setup 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",
  }