| commit | 566005474550c2c8aef2d98a81793295d5fcf94d | [log] [tgz] |
|---|---|---|
| author | Amithash Prasad <amithash@meta.com> | Thu Feb 27 13:30:55 2025 -0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Mar 05 21:47:06 2025 +0000 |
| tree | 4bb066d019cf51a2b98260a5b8ac7666eccab42e | |
| parent | c35b70189ddf99f23498acedf9601c312b02a42c [diff] |
Thermal: Add events for temperature based faults Define two events DeviceOverOperatingTemperature and DeviceOverOperatingTemperatureFault to indicate device thermal overrun events to provide information of their x86 equivalent PROCHOT and THERMTRIP. Change-Id: Iee45c6cdf6063c886043fe5e5b5a4ef8f434f6dd Signed-off-by: Amithash Prasad <amithash@meta.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