| commit | 78f3103dd6ffc86514b92ee0c233246a3c1db76b | [log] [tgz] |
|---|---|---|
| author | Chris Cain <cjcain@us.ibm.com> | Thu Oct 20 12:03:57 2022 -0500 |
| committer | Chris Cain <cjcain@us.ibm.com> | Mon Oct 24 08:41:32 2022 -0500 |
| tree | 021cfdcd9f9092f0f8209dea7e84aad0eacd4da2 | |
| parent | 844e332c6a85c37e3feda0e092e09cd3bee53366 [diff] |
Control.Power.CapLimits: Add power cap limits interface This interface will provide the minimum and maximum power cap values supported. This will be hosted/written by OCC.Control and is replacing the same properties from Control.Power.Cap. The properties in Control.Power.Cap are hosted by Settings and the cap limits had to temporarily be made writable so that OCC.Control could write them. Change-Id: Id24be182f7af8bfdc66d312a72b56afe172f8543 Signed-off-by: Chris Cain <cjcain@us.ibm.com>
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.
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.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir