| commit | c7560faae59f3c51404829d6f410b58034d602b8 | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Thu Nov 07 17:01:30 2024 -0800 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Mon Jan 27 19:31:26 2025 -0800 |
| tree | 77ec64955ec79f937c63e742f9b52a08072653e0 | |
| parent | 63e043d91a508e97deb8cf25e21f62cfc4fc38b4 [diff] |
add events for leak detector group Add the leak events to be reported for leak detector groups. Currently, there is no standard redfish messages registry for these events, hence adding them to openBMC namespace. ``` https://redfishforum.com/thread/1074/redfish-message-registry-leakdetection ``` Change-Id: I83aa5589426726f537c768d9ac05aa42a065abba 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