| commit | 5f4daf159232c5e5dfecc86d3742d0534701900a | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Wed Aug 14 16:30:16 2024 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 20 14:04:25 2024 -0500 |
| tree | f89d09c8a80fa05e785f75b36a6d4a8692bd0a19 | |
| parent | ad26251b29cc7eff15be621a50ae1b2450d0dd41 [diff] |
leak detector: add leak events Add the leak events to be reported for liquid leak detector. Currently, there is no standard redfish message registry for these events, hence they are being added to OpenBMC namespace. ``` https://redfishforum.com/thread/1074/redfish-message-registry-leakdetection ``` Change-Id: Ibc88dc2ecf73c4cddcf35d80b2e960026d92dfa4 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