| commit | d7a81eb567ecdb167d57be52783eca480285b60f | [log] [tgz] |
|---|---|---|
| author | Sharad Yadav <sharady@nvidia.com> | Sat May 15 22:27:28 2021 +0530 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 28 18:19:35 2021 +0000 |
| tree | c6cab79cb336360e4f4a105d7e9a53704d189e0c | |
| parent | 7b0f1172f898f75d8160075923b74a7ae534b7c0 [diff] |
Inventory: Add type attribute to Item.Accelerator interface
Inventory accelerator items can report their processor type
via management APIs like Redfish.
For this purpose, this commit adds following property:
1. Type - The string identifies the type of processor in
the socket.
Signed-off-by: Sharad Yadav <sharady@nvidia.com>
Change-Id: I0e27ddc2fe4c2115ca134091ff9de38c35423a55
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 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