Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 5c3a15636c0368453d643924f6162e15c9ce5efd
commit5c3a15636c0368453d643924f6162e15c9ce5efd[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Wed Jul 02 01:39:44 2025 -0500
committerSouvik Roy <souvikroyofficial10@gmail.com>Wed Jul 02 09:41:51 2025 -0500
tree7beb64b512fe2b4487fa0f552dac5204247b2c1d
parent079c43dcef4ad0fcf571e94d7e24b25710be7b10 [diff]
Listener:Present property callback stub

This commit adds APIs in Listener to register "Present" property change
callback for all FRUs for which vpd-manager does not handle presence and
which are hot pluggable. If such a FRU is plugged in/removed,
vpd-manager needs to detect this and collect/delete the VPD of the FRU.
Note: this is a stub implementation, and actual implementation will be
handled in future commit(s).

Change-Id: Ib7edc633bc6395976f2f3d1e4b3c5f90a6b999bc
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
3 files changed
tree: 7beb64b512fe2b4487fa0f552dac5204247b2c1d
  1. configuration/
  2. docs/
  3. scripts/
  4. service_files/
  5. test/
  6. vpd-manager/
  7. vpd-tool/
  8. vpdecc/
  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.