commit | 523dc36ac1a73bb63ecb3cbd76f7d88a9ac3481b | [log] [tgz] |
---|---|---|
author | Santosh Puranik <santosh.puranik@in.ibm.com> | Thu Feb 04 16:03:29 2021 +0530 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Apr 07 19:41:20 2021 +0000 |
tree | 7dcfe9d71dfffe433e947105e6df882fd9651dcd | |
parent | 70ee1cff21ade602590f7be9310d68a6903a5bf8 [diff] |
Inventory.Decorator.I2CDevice: Add I2CDevice Interface YAML Define a I2CDevice inventory item interface. This can be implemented by inventory objects that want to expose i2c device bus number and address on D-Bus. One example of how this interface is used can be found in the Entity Manager repo. Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: I236ea86a05f43e46605e4a6f9922156b1d15309f
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 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