| commit | bb86c6148f765fb0cf973679eae85990cba71693 | [log] [tgz] |
|---|---|---|
| author | Alexander Hansen <alexander.hansen@9elements.com> | Fri Aug 22 15:35:41 2025 +0200 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Oct 02 02:03:56 2025 +0000 |
| tree | 1ca91d79273a5497b5b3efb9589bc281d2c4e70d | |
| parent | 34fde7c0b23a322dd723d4f4998b48f43f349feb [diff] |
DevicePresence: Add 'Compatible' field This field can be populated by gpio-presence daemon to provide additional information for probing hardware in EM configs. The string may be empty in case the daemon could not find a Compatible Decorator on the parent inventory item. See the related EM change [1] for detailed explanation. References: [1] https://gerrit.openbmc.org/c/openbmc/entity-manager/+/83062 Change-Id: I2d4bd43933f04f2758c52500f074c6f8202a2c34 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