commit | d4fad16ea7ab8c953aaf526f3e6fc086f880b2bf | [log] [tgz] |
---|---|---|
author | Shounak Mitra <shounak@google.com> | Mon Aug 08 21:53:41 2022 +0000 |
committer | Shounak Mitra <shounak@google.com> | Tue Aug 09 15:53:53 2022 +0000 |
tree | af8ab8349261b780ee0ef9c0dd5ac1ba73ce90d1 | |
parent | fd26ad1e38942d2b5008c40b29e89bc7d233ed94 [diff] |
inventory: sensors: Document related inventory association This change just adds the associations that are already documented here to the YAML: https://github.com/openbmc/docs/blob/master/architecture/sensor-architecture.md#association-type-2-linking-a-low-level-hardware-item-to-its-sensors Change-Id: I4dd23e842a6dd7e702f372efd0f192d28bfbf13b Signed-off-by: Shounak Mitra <shounak@google.com>
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 and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir