commit | 589c181a345406e5764084aa177e0616e212b44f | [log] [tgz] |
---|---|---|
author | Shawn McCarney <shawnmm@us.ibm.com> | Thu Jan 14 12:13:26 2021 -0600 |
committer | Shawn McCarney <shawnmm@us.ibm.com> | Thu Jan 21 16:09:02 2021 +0000 |
tree | 7051ec8f28dd04e833feed44d9a90a02fee5b1fa | |
parent | 860d51af90dadb591b314a834a6cdc47532536c6 [diff] |
regulators: Obtain config file name from D-Bus Determine the correct JSON configuration file name based on the values in the D-Bus compatible systems interface. Also support a default configuration file name for systems that do not use the compatible systems interface. Tested: * Verified correct config file name found on Rainier system * When phosphor-regulators starts before entity-manager * When phosphor-regulators starts after entity-manager * Verified correct config file name found on Everest system * When phosphor-regulators starts before entity-manager * When phosphor-regulators starts after entity-manager * Error cases * For full test plan see https://gist.github.com/smccarney/2dbc81aa55e3fa6250f0827eab62fff7 Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com> Change-Id: I98902116b55297085ca3c40ce48f40972c3a3827
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", }