| commit | ec18d808021c9e1634ea8e7b9fddb7b549bda257 | [log] [tgz] |
|---|---|---|
| author | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed Jun 02 01:52:58 2021 -0500 |
| committer | gikrish1 <gikrish1@in.ibm.com> | Tue Jan 23 05:04:25 2024 +0000 |
| tree | d3164a4ae0666010eab84471ecb9b7fef6b3bbc7 | |
| parent | 2c872b3c4bb9adde1e1bebc748da8e221a1f90a2 [diff] |
IBM: Api to collect single FRU VPD An api to collect VPD of a given FRU by launching the parser exe asynchronously. It can be used to collect VPD of any given FRU in case of concurrent maintenance. As a pre-requisite for this api, deleteFRUVPD api needs to be called for that particular FRU. As this api makes async call to the parser, caller needs to register for Present property change signal for that FRU on DBus to ensure successful execution of VPD parser for that FRU. The caller is also suggested to have a timer of around two mins at their end and in case the present property is not set to true in that timeline, can mark the call as failed. Change-Id: Ia0dff5825ff3e0f9214d5212f1151023568e5a2d Signed-off-by: Sunny Srivastava <sunnsr25@in.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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir