| commit | 0372ac941861604339637ca3db81f9b4ce2733d7 | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Fri Jul 25 18:06:02 2025 -0700 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Wed Sep 24 13:44:38 2025 -0700 |
| tree | eee272f2d0edc265ec9631434f6e0a7dfa6fc8c1 | |
| parent | 1f7befd2490bed95e38efa75a540cbdbb9823600 [diff] |
sensor events: add internal threshold level events In certain scenarios, the threshold monitoring is done internally by the hardware and no thresholds values are available for the software to consume. In such scenarios, add internal level based events as per Redfish SensorEvent schema [1]. [1] https://github.com/DMTF/Redfish-Publications/blob/main/registries/SensorEvent.1.0.1.json#L306 Change-Id: I61c9375b6fd0347084f08e770b86c349a1eecabb Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
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 and org/freedesktop 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