| commit | 8c79b1dc0270d01c0b713a345c8ec39533c542e4 | [log] [tgz] |
|---|---|---|
| author | Nikhil Namjoshi <nikhilnamjoshi@google.com> | Tue Aug 09 03:09:32 2022 +0000 |
| committer | Nikhil Namjoshi <nikhilnamjoshi@google.com> | Thu Oct 27 18:07:21 2022 +0000 |
| tree | a46893b33cbe76a466d6604e3d2aee6820c3094e | |
| parent | b78a070484513df432e60deec60bd146c9afddf0 [diff] |
Inventory : Add Association interface for Cpu and Core The change #38570 in bmcweb, uses associations between Cpu and CpuCore. So document those associations in phosphor-dbus-interfaces Change-Id: I5b12ca5a89c094e2a5b47a7fbc39482d6286e9d3 Signed-off-by: Nikhil Namjoshi <nikhilnamjoshi@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