| commit | 2c33a8992449471f566fdfdaa629fae27ac572f8 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 04 12:14:13 2020 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 04 12:41:08 2020 -0600 |
| tree | 8e8863a9ca66039faedfa2b3cf28ff6a10bd4466 | |
| parent | 1d4979c7e3996a4ab80915f320536cc9e78f41e8 [diff] |
Threshold: define values to represent un-set threshold Some existing implementations were using the value 0 to indicate an unset threshold, but this makes it impossible to have a threshold of 0. Zero is a reasonable threshold for some sensors, such as a lower-bound on a temperature sensor. Specify that 'NaN' should be used to represent thresholds which are not defined. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I518b4b77a5f7601ea7079980f77c31991f6f9dde
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