| commit | f71c358197f780ed0d1d07a285d433f159fa9b65 | [log] [tgz] |
|---|---|---|
| author | Daniel Hsu <Daniel-Hsu@quantatw.com> | Fri Jun 06 16:29:17 2025 +0800 |
| committer | Daniel Hsu <Daniel-Hsu@quantatw.com> | Fri Jun 06 16:29:17 2025 +0800 |
| tree | 9c18b4853c876aa784de9f38d95d6809276117bf | |
| parent | 3e4d26604b856a210a3fe1188ae56fc050dde1c1 [diff] |
com.meta: add device-specific suffixes to Harma CPLD compatible strings The CPLDs in the system might not share the same image with the same chip; add a suffix to distinguish them. Change-Id: Ia3e93c8da557c84fd46b67ec4a279977649d7d39 Signed-off-by: Daniel Hsu <Daniel-Hsu@quantatw.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