Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 7b7a5632c594d60f4620ca14379a766a56faf846
commit7b7a5632c594d60f4620ca14379a766a56faf846[log] [tgz]
authorShawn McCarney <shawnmm@us.ibm.com>Wed Nov 19 13:08:58 2025 -0600
committerShawn McCarney <shawnmm@us.ibm.com>Thu Nov 20 15:05:04 2025 -0600
treed32e913cd64c5c77b63b68ca48893357d1d5fe55
parente6d7f4cb088171139a2ca33e71137806d887da8d [diff]
pseq: Support "GPIOs only" power sequencer device

Add support for a "GPIOs only" power sequencer device to the
phosphor-power-sequencer application.

If this device type is specified in the JSON configuration file, then
the application will only use the named GPIOs to power the device on/off
and read the power good signal. No attempt will be made to communicate
with the device otherwise. No pgood fault isolation will be performed.

This device type is useful for simple systems that do not require pgood
fault isolation. It is also useful as a temporary solution when
performing early bring-up work on a new system.

Tested:
* Ran automated tests

Change-Id: Ib5ba9a9c136dd5f5e853372f881f9e227f01a6bd
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
7 files changed
tree: d32e913cd64c5c77b63b68ca48893357d1d5fe55
  1. cold-redundancy/
  2. example/
  3. org/
  4. phosphor-chassis-power/
  5. phosphor-power-sequencer/
  6. phosphor-power-supply/
  7. phosphor-regulators/
  8. power-sequencer/
  9. power-supply/
  10. services/
  11. subprojects/
  12. test/
  13. tools/
  14. .clang-format
  15. .clang-tidy
  16. .clang-tidy-ignore
  17. .gitignore
  18. .shellcheck
  19. compatible_system_types_finder.cpp
  20. compatible_system_types_finder.hpp
  21. config_file_parser_error.hpp
  22. dbus_interfaces_finder.cpp
  23. dbus_interfaces_finder.hpp
  24. device.hpp
  25. device_monitor.hpp
  26. elog-errors.hpp
  27. file_descriptor.hpp
  28. format_utils.hpp
  29. gpio.cpp
  30. gpio.hpp
  31. json_parser_utils.cpp
  32. json_parser_utils.hpp
  33. LICENSE
  34. meson.build
  35. meson.options
  36. names_values.hpp
  37. OWNERS
  38. pmbus.cpp
  39. pmbus.hpp
  40. README.md
  41. temporary_file.cpp
  42. temporary_file.hpp
  43. temporary_subdirectory.cpp
  44. temporary_subdirectory.hpp
  45. types.hpp
  46. utility.cpp
  47. utility.hpp
README.md

phosphor-power

Overview

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

Actively-maintained applications:

  • cold-redundancy: Application that makes power supplies work in Cold Redundancy mode and rotates them at intervals.
  • phosphor-chassis-power: JSON-driven application that monitors chassis power on multi-chassis systems.
  • phosphor-power-sequencer: JSON-driven application that powers the chassis on/off and monitors the power sequencer device.
  • phosphor-power-supply: Next generation power supply monitoring application.
  • phosphor-regulators: JSON-driven application that configures and monitors voltage regulators.
  • tools/power-utils: Power supply utilities.

Legacy applications:

  • power-sequencer: Original power sequencer monitoring application.
  • power-supply: Original power supply monitoring application.

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/<driver>.<instance>/
    • 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",
  }