commit | 03e2a02869b7d2208396c7334eea3e2333a6a16b | [log] [tgz] |
---|---|---|
author | Faisal Awada <faisal@us.ibm.com> | Wed Nov 15 20:31:13 2023 +0000 |
committer | Faisal Awada <faisal@us.ibm.com> | Fri Nov 17 20:42:39 2023 +0000 |
tree | c49587491fdafeddfdc5d5fd705b850f01c4ddde | |
parent | b7131a12ee603264a90b55dd7afde929434424e9 [diff] |
psu-ng: Fixed PSU monitor app not to report error on valid configuration Modified the PSU monitor app not to report error when the PSU is not present and the PSU validation timer active; or PSU present but we don't have infomation from Entity Manager (EM),the application will have to wait for EM info while the validation timer active before reporting error. Note: The fix was done due to sometime Entity manager gets busy may delay to post PSU information which causes this application to post invalid PSU error. Tested: 1 - On system with 4 PSUs and chassis powered on, with modified code to allow 3 PSU interfaces and ignore the 4th interface. * Verified error reported after the validation timer expired. 2 - On system requires 4 PSUs I removed 1 PSU, powered on the chassis rebooted BMC with the fix. * Verified the system reported error after the validation timer expired. 3 - Ran a good machine pass with the fix and verified no error reported. Change-Id: I7c99f64b589fbe7db86cb16b720cf3ff9b62baab Signed-off-by: Faisal Awada <faisal@us.ibm.com>
This repository contains applications for configuring and monitoring devices that deliver power to the system.
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:
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/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", }