commit	212543969f6e4a5908f7f2e017f59adcce7ae723	[log] [tgz]
author	Andrew Geissler <geissonator@yahoo.com>	Wed Apr 02 10:25:39 2025 -0500
committer	Shawn McCarney <shawnmm@us.ibm.com>	Fri Apr 04 13:50:08 2025 +0000
tree	537492c10219f8739eaac110d2da0f7e61b1d524
parent	71172458ba5c9f78c5a1a206f4533c806081ed12 [diff]

power-sequencer: make pgood timeout configurable

The IBM system1 utilizes a FPGA to power on and off the chassis. This
FPGA can take up to 10 seconds to power on and on occasion it hits the
default 10s timeout, causing an error log to be logged.

Make the pgood timeout configurable so systems can override the timeout
if needed.

Tested:
- Confirmed by default config.h had 10 for the PGOOD_TIMEOUT
- Confirmed when overrode to 30 in a bbappend that it changed to 30
  within the config.h

Change-Id: I31ef65ee9f331c4690d68789e435241539804221
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>

3 files changed

tree: 537492c10219f8739eaac110d2da0f7e61b1d524

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