commit | 348168b6ee83b4d1c4d83e47c651e3d51e4f614b | [log] [tgz] |
---|---|---|
author | Faisal Awada <faisal@us.ibm.com> | Tue Jul 08 11:23:02 2025 -0500 |
committer | Faisal Awada <faisal@us.ibm.com> | Tue Jul 29 15:38:15 2025 -0500 |
tree | 0bb30f57559e49f97c0cf243e0ca23f1a0758a60 | |
parent | f661ecb9383c25986a8769f9b5b65d13993437b0 [diff] |
chassis-psu: ChassisManager class to manage chassis PSUs Introduced the ChassisManager class to detect chassis and manage power supply devices associated with chassis using D-Bus interfaces. This includes: - Subscribing to Entity Manager interface changes - Implementing timers to validate power supply presence and status - Scan the system for new chassis; if a chassis is new, add it to the chassis list. - Adding event loop integration for continuous monitoring - Analysis of power supply status and error logging. Test: - On simulation system, verified chassis and their power supplies are added to the chassis list, with each power supply correctly linked to its corresponding chassis. - Verified the power supplies in each chassis based on analysis performed at the specified time interval. Note: There are some commented code indicates future implementation, please ignore for now, as they will be implemented soon. Change-Id: I80c271783e71f668ca1405f7aca80c8ec112f531 Signed-off-by: Faisal Awada <faisal@us.ibm.com>
This repository contains applications for configuring and monitoring devices that deliver power to the system.
Actively-maintained applications:
Legacy applications:
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:
Several applications in this repository require a PSU JSON config to run. The JSON config file provides information for:
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:
/sys/bus/i2c/devices/3-0069/
/sys/bus/i2c/devices/3-0069/hwmon/hwmonX/
/sys/kernel/debug/pmbus/hwmonX/
/sys/kernel/debug/<driver>.<instance>/
/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", }