| commit | 70ee1cff21ade602590f7be9310d68a6903a5bf8 | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Thu Jan 21 15:25:59 2021 -0600 |
| committer | Matt Spinler <spinler@us.ibm.com> | Fri Mar 26 09:32:12 2021 -0500 |
| tree | bb75190f716120ad90d80531cc9c739b06d575d3 | |
| parent | ae956ad9efd2be24c5439a4ef6498fb5c8383719 [diff] |
thresholds: Add threshold alarm signals Define signals on every sensor threshold interface that can be sent when a threshold alarm value changes. The signal contains the sensor value that caused the alarm change. <Threshold Name>HighAlarmAsserted: * Sent when the Warning/Critical/etc AlarmHigh property is asserted <Threshold Name>HighAlarmDeasserted: * Sent when the Warning/Critical/etc AlarmHigh property is deasserted <Threshold Name>LowAlarmAsserted: * Sent when the Warning/Critical/etc AlarmLow property is asserted <Threshold Name>LowAlarmDeasserted: * Sent when the Warning/Critical/etc AlarmLow property is deasserted The threshold name, like 'Critical', is in the property name so that the generated C++ names are unique and a class can implement multiple thresholds at once. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ib58fccc5fcb71a55a79ac74c0113326bd8e40219
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