| commit | e123c4615275434429ecb493a84384c5ad965ec0 | [log] [tgz] |
|---|---|---|
| author | Tom Joseph <rushtotom@gmail.com> | Wed May 05 03:36:01 2021 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 07 12:02:01 2021 +0000 |
| tree | edb4dc1b69559c168e8d7b0bc3741c080aa9f400 | |
| parent | 5167e22a72ec4633dbaf2a9450a337dd8a5ac680 [diff] |
MCTP: Define interface for MCTP endpoint enumeration This interface will be implemented by an MCTP control message protocol process[1] that discovers MCTP communication terminuses that are discoverable by BMC. D-Bus discovery of this interface triggers higher level protocols like PLDM to complete the PLDM discovery for the MCTP devices. [1] https://github.com/openbmc/docs/blob/master/designs/mctp/mctp-kernel.md Signed-off-by: Tom Joseph <rushtotom@gmail.com> Change-Id: I240bd3e7d300dfbc0a74ed71eb5a466e1d4a1db4
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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir