| commit | 60040679038171a2f997fa62cc195a32e8a18bba | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Fri Jul 25 18:20:51 2025 -0700 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Wed Sep 24 13:48:20 2025 -0700 |
| tree | b8330fbcb555db877f5ad1db983374f253ec9ad2 | |
| parent | 0372ac941861604339637ca3db81f9b4ce2733d7 [diff] |
move non-threshold events into sensor namespace Move the non-threshold events into the sensor namespace so they don't include threshold in their interface name. These events are generic sensor events and have no relation to threshold monitoring. I verified in the openBMC code and there has been no user of these events for now, hence they are safe to move. Change-Id: I5aa6a5bdda04f520f842107c2e7a3537e04f821a 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