Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / refs/heads/master
commitb7878e55662bafbf28581c5b3b677207195fb8b3[log] [tgz]
authorFaisal Awada <faisal@us.ibm.com>Wed Nov 26 15:20:50 2025 -0600
committerShawn McCarney <shawnmm@us.ibm.com>Thu Jan 08 15:46:13 2026 +0000
treef6dee3290b5c27444db7fda97cfe04d5ca1c642e
parentebbeb63f5e051597b96b8d8a8ac615a5f162dc23 [diff]
chassis-psu: Clear brownout,determine required PSU

Update logic so PowerSystemInputs status is set to good only when the
chassis power state is off. This update adds a check for powerState off
before setting the status to good, ensuring the brownout is properly
cleared.

Add logic to getRequiredPSUCount which calculates the minimum required
PSU count based on the model used and supported configurations.

Implements the Chassis::getRequiredPSUCount() to determines the
necessary number of power supplies by:

1. Collecting the model names of all present PSUs.
2. Checking if exactly one model is found (assuming all PSUs have same
   model)
3. Looking up the corresponding configuration in `supportedConfigs` to
   retrieve the required count.
4. Return 0 if no configuration loaded or no model.

Test:
  The following tests were done in simulated environment and forced some
  logic to execute certain part of the code:
  - During brownout Validate PowerSystemInputs status set to good when
    the chassis power state is off.
  - Validate present PSU count meet the minimum PSU required in the
    configuration.

Change-Id: I55fc7a62242a449f7d1c6d897a91bd5798b20964
Signed-off-by: Faisal Awada <faisal@us.ibm.com>
5 files changed
tree: f6dee3290b5c27444db7fda97cfe04d5ca1c642e
  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. chassis_status_monitor.cpp
  20. chassis_status_monitor.hpp
  21. compatible_system_types_finder.cpp
  22. compatible_system_types_finder.hpp
  23. config_file_parser_error.hpp
  24. dbus_interfaces_finder.cpp
  25. dbus_interfaces_finder.hpp
  26. device.hpp
  27. device_monitor.hpp
  28. elog-errors.hpp
  29. file_descriptor.hpp
  30. format_utils.hpp
  31. gpio.cpp
  32. gpio.hpp
  33. json_parser_utils.cpp
  34. json_parser_utils.hpp
  35. LICENSE
  36. meson.build
  37. meson.options
  38. names_values.hpp
  39. OWNERS
  40. pmbus.cpp
  41. pmbus.hpp
  42. README.md
  43. temporary_file.cpp
  44. temporary_file.hpp
  45. temporary_subdirectory.cpp
  46. temporary_subdirectory.hpp
  47. types.hpp
  48. utility.cpp
  49. 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",
  }