Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 3afa711d1c567f89445e9edfe0fa5aa9ac7aafb5
commit3afa711d1c567f89445e9edfe0fa5aa9ac7aafb5[log] [tgz]
authorBob King <Bob_King@wistron.com>Thu Mar 19 09:35:31 2020 +0800
committerBob King <Bob_King@wistron.com>Thu Mar 19 09:43:48 2020 +0800
tree50df500b5683d096429c6959b365a007c5e4ada2
parent3f1242f3a147ee372d1e5c7274cb1db69d626b34 [diff]
regulators: Add test cases for action.

Add test cases for action:
  * Valid: Comments property not specified
  * Valid: Comments property specified
  * Valid: and action type specified
  * Valid: compare_presence action type specified
  * Valid: compare_vpd action type specified
  * Valid: i2c_compare_bit action type specified
  * Valid: i2c_compare_byte action type specified
  * Valid: i2c_compare_bytes action type specified
  * Valid: i2c_write_bit action type specified
  * Valid: i2c_write_byte action type specified
  * Valid: i2c_write_bytes action type specified
  * Valid: if action type specified
  * Valid: not action type specified
  * Valid: or action type specified
  * Valid: pmbus_read_sensor and pmbus_write_vout_command action type specified
  * Valid: run_rule action type specified
  * Valid: set_device action type specified
  * Invalid: Wrong data type for comments (should be array of string)
  * Invalid: Wrong data type for action type
  * Invalid: Empty comments array
  * Invalid: Comments array has wrong element type (should be string)
  * Invalid: No action type specified
  * Invalid: Multiple action types specified
  * Invalid: Unexpected property specified

Signed-off-by: Bob King <Bob_King@wistron.com>
Change-Id: I81dfb50cf46a3091753f43266af8dc01527d621d
2 files changed
tree: 50df500b5683d096429c6959b365a007c5e4ada2
  1. cold-redundancy/
  2. example/
  3. org/
  4. phosphor-power-supply/
  5. phosphor-regulators/
  6. power-sequencer/
  7. power-supply/
  8. services/
  9. test/
  10. tools/
  11. .clang-format
  12. .gitignore
  13. argument.hpp
  14. device.hpp
  15. device_monitor.hpp
  16. elog-errors.hpp
  17. file.hpp
  18. gpio.cpp
  19. gpio.hpp
  20. LICENSE
  21. MAINTAINERS
  22. meson.build
  23. meson_options.txt
  24. names_values.hpp
  25. pmbus.cpp
  26. pmbus.hpp
  27. README.md
  28. types.hpp
  29. utility.cpp
  30. utility.hpp
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",
  }