| commit | 534515b7ca4cea7dfcf151882bc5987fef3f94d5 | [log] [tgz] |
|---|---|---|
| author | Zhichuang Sun <zhichuang@google.com> | Mon Jun 12 14:36:31 2023 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Feb 29 02:30:46 2024 +0000 |
| tree | 64836621f5512d36ab5a9cce54facb4024f3be75 | |
| parent | 387a6191f225335caa052522b4774cdb70853189 [diff] |
Add TrustedComponent D-bus Interface TrustedComponent represents a trusted device, such as a TPM or SPDM-capable device. This commit adds TrustedComponent D-Bus interface. Change-Id: Ic5de5ee6c8ffd58d50a64937dacdddbebac7f1ab Signed-off-by: Zhichuang Sun <zhichuang@google.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