| commit | 86f8c536e4f9da7e1f3e549449999b07c1038ae7 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 01 06:34:04 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 01 06:34:18 2021 -0500 |
| tree | 4097d2380e30d8e5ad3f9f4db8f50a3900f856a7 | |
| parent | 3c5b76491afb8401627fc343077fe420f8a5e7f9 [diff] |
threshold: fix up documentation per sensor.value The Sensor.Value has a list of "recognized hierarchies" which is similarly replicated in all of the Threshold interfaces. The lists in the Threshold objects were incomplete, so update them. Also, make trivial whitespace / formatting changes to ensure linewrap is at the appropriate (80) columns. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I6bd76ca423e1ea3c2e0c7ce59e10dce1125eb6d1
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