| commit | 15eeb50d101aa3aa48f4aa516979a6733034b125 | [log] [tgz] |
|---|---|---|
| author | Jonathan Doman <jonathan.doman@intel.com> | Mon Oct 26 21:38:53 2020 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 04 19:01:56 2020 +0000 |
| tree | 4e6def4d1e9508e6215527ece4eb3300962a062d | |
| parent | a7a6db3f770f5a1a5fd660ba3f6a611c435db616 [diff] |
Define Errors on CurrentOperatingConfig properties There are some conditions which would prevent changes to the CurrentOperatingConfig interface on a CPU. To make it easier for a user to know their property Set was rejected, define some common error codes to return. Signed-off-by: Jonathan Doman <jonathan.doman@intel.com> Change-Id: I7a1d3a8c0194a5c2f7b275d779915d2c2c72c530
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 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