188db7d8f3d608e3c0cb71360586ec0b12aaa27b - openbmc/phosphor-power

commit	188db7d8f3d608e3c0cb71360586ec0b12aaa27b	[log] [tgz]
author	Bob King <Bob_King@wistron.com>	Fri Jan 31 13:01:01 2020 +0800
committer	Shawn McCarney <shawnmm@us.ibm.com>	Fri Feb 21 13:26:03 2020 +0000
tree	d542384ac083c15828053d90a0205723b6baf3e2
parent	64df7daada86078e387f2d1f3b73310d2b4b9c09 [diff]

regulators: Add test cases for 'i2c_write_bit' and 'i2c_write_byte(s)'.

i2c_write_bit test cases:
*Valid: test rule i2c_write_bit.
*Invalid: test i2c_write_bit with no register.
*Invalid: test i2c_write_bit with no position.
*Invalid: test i2c_write_bit with no value.
*Invalid: test i2c_write_bit with register wrong type.
*Invalid: test i2c_write_bit with register wrong format.
*Invalid: test i2c_write_bit with position wrong type.
*Invalid: test i2c_write_bit with position greater than 7.
*Invalid: test i2c_write_bit with position less than 0.
*Invalid: test i2c_write_bit with value wrong type.
*Invalid: test i2c_write_bit with value greater than 1.
*Invalid: test i2c_write_bit with value less than 0.
i2c_write_byte test cases:
*Valid: test i2c_write_byte with all properties
*Valid: test i2c_write_byte with all required properties
*Invalid: test i2c_write_byte with no register
*Invalid: test i2c_write_byte with no value
*Invalid: test i2c_write_byte with property register wrong type
*Invalid: test i2c_write_byte with property value wrong type
*Invalid: test i2c_write_byte with property mask wrong type
*Invalid: test i2c_write_byte with property register more than 2 hex digits.
*Invalid: test i2c_write_byte with property value more than 2 hex digits.
*Invalid: test i2c_write_byte with property mask more than 2 hex digits.
*Invalid: test i2c_write_byte with property register less than 2 hex digits.
*Invalid: test i2c_write_byte with property value less than 2 hex digits.
*Invalid: test i2c_write_byte with property mask less than 2 hex digits.
*Invalid: test i2c_write_byte with property register no leading prefix.
*Invalid: test i2c_write_byte with property value no leading prefix.
*Invalid: test i2c_write_byte with property mask no leading prefix.
*Invalid: test i2c_write_byte with property register invalid hex digit.
*Invalid: test i2c_write_byte with property value invalid hex digit.
*Invalid: test i2c_write_byte with property mask invalid hex digit.
i2c_write_bytes test cases:
*Valid: test i2c_write_bytes
*Valid: test i2c_write_bytes with all required properties
*Invalid: test i2c_write_bytes with no register
*Invalid: test i2c_write_bytes with no values
*Invalid: test i2c_write_bytes with property values as empty array
*Invalid: test i2c_write_bytes with property masks as empty array
*Invalid: test i2c_write_bytes with property register wrong type
*Invalid: test i2c_write_bytes with property values wrong type
*Invalid: test i2c_write_bytes with property masks wrong type
*Invalid: test i2c_write_bytes with property register more than 2 hex digits.
*Invalid: test i2c_write_bytes with property value more than 2 hex digits.
*Invalid: test i2c_write_bytes with property mask more than 2 hex digits.
*Invalid: test i2c_write_bytes with property register less than 2 hex digits.
*Invalid: test i2c_write_bytes with property value less than 2 hex digits.
*Invalid: test i2c_write_bytes with property mask less than 2 hex digits.
*Invalid: test i2c_write_bytes with property register no leading prefix.
*Invalid: test i2c_write_bytes with property value no leading prefix.
*Invalid: test i2c_write_bytes with property mask no leading prefix.
*Invalid: test i2c_write_bytes with property register invalid hex digit.
*Invalid: test i2c_write_bytes with property value invalid hex digit.
*Invalid: test i2c_write_bytes with property mask invalid hex digit.

Signed-off-by: Bob King <Bob_King@wistron.com>
Change-Id: I7d9593605985ad466f6e32df7cbf23d6e513f991

phosphor-regulators/test/validate-regulators-config_tests.cpp[diff]

1 file changed

tree: d542384ac083c15828053d90a0205723b6baf3e2

README.md

Code for detecting and analyzing power faults on Witherspoon.

To Build

To build this package, do the following steps:

    1. meson build
    2. ninja -C build

To clean the repository again run `rm -rf build`.

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