Power.Cap: add properties to control Power Limit

Based on the chapter 6.6 - Power management of DCMI specification, BMC
needs more information to control Power Lmit.

This commit adds 3 properties to control Power Limit, the list of
added properties as below:
  1. ExceptionAction: Exception Action
  2. CorrectionTime: Correction time in microseconds
  3. SamplingPeriod: Sampling period in microseconds

Those properties are used to monitor total power consumption, depending
on the user's configuration, BMC can turn off the power/log event only
or do nothing when the total power consumption is greater than the power
limit.

Change-Id: I981f06855d6a55b1207541c84d53d774d0d25491
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
1 file changed
tree: c801c1c8cedd67300ea62b138b50e3ac3e8654e4
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. .shellcheck
  8. LICENSE
  9. meson.build
  10. meson_options.txt
  11. OWNERS
  12. README.md
  13. requirements.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.

Building

This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.

The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References