Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 25478fa2258ba98bbe5de74e420fe8557841926c
commit25478fa2258ba98bbe5de74e420fe8557841926c[log] [tgz]
authorShawn McCarney <shawnmm@us.ibm.com>Tue Aug 01 17:25:07 2023 -0500
committerShawn McCarney <shawnmm@us.ibm.com>Mon Aug 21 19:17:28 2023 +0000
treed82c5308bb2d4042741ef40a134d9cc4adcc8e72
parentb0475e7a5688fd9ab5c670adc630ad53d7de8607 [diff]
pseq: Create Bonnell configuration file

Create the power sequencer configuration file for Bonnell systems.  This
file identifies the PMBus rails and the GPIO lines/pins that should be
checked when a pgood failure occurs.

On Bonnell systems no GPIO lines need to be checked.

Tested:
* Configuration file loading
  * Verified file is found on Bonnell systems using D-Bus property
  * Verified file is loaded successfully without errors
  * Verified all rails in file are stored in C++ data structures
  * Verified having empty pin array does not cause an error
  * Tested where file contains a syntax error
    * Verified error message is written to journal
    * Verified no error log created
* pgood detection
  * Verified system powers on cleanly when no pgood error is present
    * chassison
      * Verified chassis is powered on
      * Verified no error logs created
      * Verified no error messages written to the journal
    * poweron
      * Verified system is powered on
      * Verified no error logs created
      * Verified no error messages written to the journal
  * Verified system powers off cleanly when no pgood error is present
    * chassisoff
      * Verified chassis is powered off
      * Verified no error logs created
      * Verified no error messages written to the journal
    * poweroff
      * Verified system is powered off
      * Verified no error logs created
      * Verified no error messages written to the journal
  * Test where a pgood error is detected in a rail
    * Verified pgood failure is detected
    * Verified error message written to the journal
    * Verified GPIO values written to the journal
    * Verified error log is created
    * Tested with a pgood error on each rail in the config file
  * Test where pgood failure occurs during power on attempt
  * Test where pgood failure occurs after system was successfully
    powered on

Change-Id: I431d2dd7e99f2a99bbab936d6fad03af5654886f
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
1 file changed
tree: d82c5308bb2d4042741ef40a134d9cc4adcc8e72
  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. argument.hpp
  17. device.hpp
  18. device_monitor.hpp
  19. elog-errors.hpp
  20. file_descriptor.hpp
  21. gpio.cpp
  22. gpio.hpp
  23. LICENSE
  24. meson.build
  25. meson_options.txt
  26. names_values.hpp
  27. OWNERS
  28. pmbus.cpp
  29. pmbus.hpp
  30. README.md
  31. types.hpp
  32. utility.cpp
  33. 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",
  }