commit | 3bad9a1685b26c791b4df73a0d53770af1ac8746 | [log] [tgz] |
---|---|---|
author | Alexander Hansen <alexander.hansen@9elements.com> | Wed Nov 06 12:28:26 2024 +0100 |
committer | Patrick Williams <patrick@stwcx.xyz> | Mon Jan 27 17:15:09 2025 +0000 |
tree | d3a3b75b12340a375e273482cf6b0908fffa7c30 | |
parent | 3ad8e4b09fb8374a69988abbe5c683bb4ceebad9 [diff] |
Inventory.Source: Add DevicePresence interface Dbus interface needed for the gpio hw inventory design [1]. This interface allows to use the presence of any device to be used as an inventory source. The motivating use-case is for hardware detected via gpios. [1] https://github.com/openbmc/docs/blob/abbf7355231fbd9d5231e136780c167f2a89494e/designs/inventory/gpio-based-hardware-inventory.md Change-Id: I2d4a80498acbca46c834d2c3f093098098415a35 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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir