Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 8f08f5ac9fff03045be817b723cf29f781e1e628
commit8f08f5ac9fff03045be817b723cf29f781e1e628[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Fri Aug 29 13:17:49 2025 +0000
committerSunnySrivastava <sunnsr25@in.ibm.com>Wed Sep 03 14:06:18 2025 +0000
tree91382a0d6ac44024afbae2980421f8ef686d9a43
parentc0c007de496f738e9c23e12c5246335c7a1baf49 [diff]
Remove vpd-manager automatic FRU VPD collection

This commit removes the automatic FRU VPD collection from vpd-manager
flow. Currently, vpd-manager triggers FRU VPD collection after system
VPD has been collected. For PST systems, the FRU VPD collection needs to
be triggered externally from wait-vpd-parsers.service on active BMC
once system has reached a specific state.

Test:
```
- Patch vpd-manager executable into rainiest simics
- Restart vpd-manager
- Observe system VPD is collected but FRU VPD is not started
- Observe FRU VPD CollectionStatus property is "NotStarted"
- Now restart wait-vpd-parsers.service, and observe FRU VPD collection
  is started.
- Once wait-vpd-parsers.service exits successfully, observe FRU VPD
  CollectionStatus property is "Completed"
```

Change-Id: I74e843b22c41182ef2704f0ae01918678f1fa79d
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
2 files changed
tree: 91382a0d6ac44024afbae2980421f8ef686d9a43
  1. configuration/
  2. docs/
  3. service_files/
  4. test/
  5. vpd-manager/
  6. vpd-tool/
  7. vpdecc/
  8. wait-vpd-parser/
  9. .clang-format
  10. .gitignore
  11. LICENSE
  12. meson.build
  13. meson.options
  14. OWNERS
  15. 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.