Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 995e1c23ddd2f6a15179041be01caefaed0e9776
commit995e1c23ddd2f6a15179041be01caefaed0e9776[log] [tgz]
authorSunny Srivastava <sunnsr25@in.ibm.com>Thu Aug 28 03:13:00 2025 -0500
committerSunnySrivastava <sunnsr25@in.ibm.com>Fri Aug 29 06:39:08 2025 +0000
treebfaf96f21da714040710cc0b2cd2030308e134ae
parent48f297b0b7bb968f7e72600e043d8c5035fc1708 [diff]
Capture time stamp for FRU collection

The commit adds code to capture start and end time with respect to VPD
collection of respective FRU.
This information will help in troubleshooting efficiency issue as well
as improving performance in case required.

Change-Id: I91977b981dd6fbed7db565721457f0bb5dc704dd
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
3 files changed
tree: bfaf96f21da714040710cc0b2cd2030308e134ae
  1. configuration/
  2. docs/
  3. scripts/
  4. service_files/
  5. test/
  6. vpd-manager/
  7. vpd-tool/
  8. vpdecc/
  9. wait-vpd-parser/
  10. .clang-format
  11. .gitignore
  12. LICENSE
  13. meson.build
  14. meson.options
  15. OWNERS
  16. README.md
README.md

Overview

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 at a broken link.

The repository consists of two distinct applications, which are:

OpenPower VPD Parser

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 supported records and keywords.
  • How VPD data is translated into D-Bus interfaces and properties.

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.

IBM VPD Parser

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:

  • It parses all the records and keywords from the VPD, including large keywords (Keywords that begin with a # and are > 255 bytes in length).
  • It relies on a runtime JSON configuration (see examples/inventory.json) to determine the D-Bus object path(s) that hold interfaces and properties representing the VPD for a given VPD file path.

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.

TODOs and Future Improvements

  1. The long-term goal is to completely do away with the build time YAML driven configurations and instead reconcile the OpenPower VPD parser and the IBM VPD parser applications into a single runtime JSON driven application.
  2. Add details to the README on how to configure and build the application.
  3. More JSON documentation.
  4. Support for more IBM VPD formats.
  5. VPD Write and tool documentation.