| commit | 45ed88d80b43ea9f12e17bc5473cbc07f370bdde | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Fri Nov 20 11:33:16 2020 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jan 12 21:53:09 2021 +0000 |
| tree | 67ea9ec3af8c2ad499129a10c5be0e246bc19016 | |
| parent | a57b7e1a0d95fdc17856e08d31a04cb3a1fde7ea [diff] |
thresholds: Add 2 new threshold interfaces Add HardShutdown and SoftShutdown threshold interfaces. These could be used when a hard shutdown or soft shutdown would be necessary based on a sensor value and the existing warning and critical thresholds are already being used for other actions on that sensor. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I81c620cd46503903e36261502cdeffa35cd7cbe5
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