| commit | a3bd9f4681c313c3a7dc5ddd3743330ace57275e | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@codeconstruct.com.au> | Tue Mar 05 14:20:20 2024 +1030 |
| committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Wed Mar 27 23:27:32 2024 +0000 |
| tree | 6081b2725f81e006f29f10dbe0a6c5ed5cc0346c | |
| parent | 7705c9e71f2e9546f6c865ddfa9f41634fd7cde2 [diff] |
MCTP.Endpoint: Document configured_by association The `configured_by` / `configures` association for MCTP endpoints is hosted by mctpreactor[1]. It provides a mechanism to traverse backwards to Entity Manager configuration objects from the D-Bus objects hosted by mctpd[2]. [1]: https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/69111 [2]: https://github.com/codeconstruct/mctp Change-Id: I33b9887cf26519a3d3ac4d6c084e5852ba134163 Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
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