| commit | 34fde7c0b23a322dd723d4f4998b48f43f349feb | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Sat Aug 30 23:53:22 2025 -0700 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Wed Sep 24 13:54:10 2025 -0700 |
| tree | 2c34811b6365dc90a7f152007b73710bacc342eb | |
| parent | f41dd9719c4004069cae14a9f31966e04f7c7906 [diff] |
fan: add event interface Add the FanFailed and FanFailed events based on Redfish specification for Fan events in Environmental namespace[1]. [1] https://github.com/DMTF/Redfish-Publications/blob/main/registries/Environmental.1.2.0.json#L635 Change-Id: I36a2153d61e38f859a2434953f745e306be291da 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