commit | 523af2e013d87a46ae31dbf5e5b9ffe5ccee339e | [log] [tgz] |
---|---|---|
author | Sunny Srivastava <sunnsr25@in.ibm.com> | Mon Feb 14 07:30:10 2022 -0600 |
committer | Sunny Srivastava <sunnsr25@in.ibm.com> | Tue Dec 13 03:32:03 2022 -0600 |
tree | feaaf437bdef397d4df81adff92dec4607fe8f6c | |
parent | cce0e65345e9ea541dd43c6c66d4feb2a7e4e4aa [diff] |
Shift to boost asio library This commit shifts vpd manager from sdbusplus event loop to boost io_context event loop. The shift was done to have a more flexible way to perform async Dbus calls. For example read/write of vpd data can be performed asynchronously. It also removes dependency of Manager class on the interface class created as a part of Phosphor-Dbus-Interface repo. Test: - Introspect com.ibm.VPD.Manager /com/ibm/VPD/Manager to ensure that all the methods exposed under com.ibm.VPD.Manager interface matches to the ones documented under PDI repo. - Make DBus call to each of the exposed api to ensure that the funcation calls are working fine. -To ensure bios handler call back is working. Stop vpd-manager service. Stop pldm service. Start vpd-manager service Start pldm service. Should recieve callback. -To ensure gpio call back std::cout were added to callback function being trigerred on timer expiration and the same were verified in journal. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: I00640f64de487d5244e8be2e7a3f3d63a013644e
This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found here.
The repository consists of two distinct applications, which are:
This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:
The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.
This parser is can be built by passing in the --enable-ibm-parser
configure option. This parser differs from the OpenPower VPD parser in the following ways:
#
and are > 255 bytes in length).Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.