commit | cd2bca45b82f9bc050d1ac5bef8f1e853bda51c4 | [log] [tgz] |
---|---|---|
author | Rekha Aparna <vrekhaaparna@ibm.com> | Thu May 22 23:20:59 2025 -0500 |
committer | vrekhaaparna <vrekhaaparna@ibm.com> | Wed Jun 04 05:00:31 2025 +0000 |
tree | 13c2f578fa95ea14a863c292d555a8ad0bf8bd51 | |
parent | 0e5e4b1afbf3545d5664de0e2de6c9bef1246131 [diff] |
Update API’s of VPD.Manager interface This commit adds following APIs to VPD.Manager interface: - API to update keyword value. - API to read keyword value. - API to get hardware path of a FRU. - Property that indicates the VPD collection status of the system. Change-Id: I12dbc254c1c318eb2133abddc0ce28576cdb0e15 Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir