| commit | 0ab726efb41343f818cce5c48cbd18a2cbc12f64 | [log] [tgz] |
|---|---|---|
| author | Kevin Tung <Kevin.Tung@quantatw.com> | Tue Sep 09 16:19:19 2025 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 19 09:10:59 2025 +0000 |
| tree | 4b17d179d89b8efa36dcffe838cbc846cb185503 | |
| parent | 561c6204550edfa3210b6e1f81e29281bc79c380 [diff] |
com.meta: yosemite5: add compatible strings for VR and TPM Add compatible device strings specific to yosemite5 VR and TPM. Change-Id: I4656b415f95e35afd93d9d5bc38810b0cf264ab0 Signed-off-by: Kevin Tung <kevin.tung.openbmc@gmail.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