commit | 4d9aaf9133899a4576ce90f704a5b5f0a20d2113 | [log] [tgz] |
---|---|---|
author | Adriana Kobylak <anoo@us.ibm.com> | Wed Jun 30 15:27:42 2021 +0000 |
committer | Adriana Kobylak <anoo@us.ibm.com> | Mon Jul 19 15:19:04 2021 +0000 |
tree | b04d916f73e80c4a8957a09cd18e066f940cd852 | |
parent | 681b2a36e646b07c26fbdd2bae8f0ee1c4f3f930 [diff] |
psu-ng: Move PSU validation logic to its own function Move the PSU validation logic into a separate function so that it can be called from additional places, such as the analyze() function, which will check if the required PSUs are present before logging an error for missing PSUs. Also use std::count_if to get the number of present PSUs to make the logic cleaner. The only difference with the new function is that there's no difference between a failure due to mismatched model names and failure due to missing PSUs. The original logic would set the validation flag on mismatched model names to not run again. The new scenario is that if EM starts after psu-monitor and there is one or more PSUs with a mismatched model name, then the same error will be created every time there's a new EM PSU interface added. Tested: Verified with debug logs that the validation logic remained the same after the change. Change-Id: Iced7afc34f566be1ce479c03639b780ecd7fdd53 Signed-off-by: Adriana Kobylak <anoo@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", }