| commit | 160f88c729493ed96b66151b5dd0b02ad192ea6a | [log] [tgz] |
|---|---|---|
| author | Alexander Hansen <alexander.hansen@9elements.com> | Wed May 21 15:54:41 2025 +0200 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Jun 16 18:28:12 2025 +0000 |
| tree | 2a964f63f28970c20d15e56a0c98b72e74aabf45 | |
| parent | e791d2b581f582f6b7197355f2a6c8f07994bd28 [diff] |
DevicePresence: define base object path Base object path for the detected devices. Patch was requested in review [1] of gpio-presence sensor. References: [1] https://gerrit.openbmc.org/c/openbmc/entity-manager/+/75627/comment/131c96a5_8897394f/ Change-Id: Ifb3d3a8f6d8ae7114222f0d52aa2599405da5d2c Signed-off-by: Alexander Hansen <alexander.hansen@9elements.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