Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 14773e8f1a19d124f4ca87f4e09d0a49e647db0e
commit14773e8f1a19d124f4ca87f4e09d0a49e647db0e[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Mon Jun 23 04:44:31 2025 -0500
committerSouvik Roy <souvikroyofficial10@gmail.com>Mon Jul 07 00:14:04 2025 -0500
treeed07345e4c91a610551e925b76de1c4f753f8179
parent3d4af4aec02fb01bfe171ed0710500a07ee99f37 [diff]
Listener: Parse correlated properties JSON

This commit adds changes in Listener class to parse correlated
properties JSON file. Listener class needs to have the parsed correlated
properties JSON in memory to listen for property changes on specific
object path, interface and update correlated property/properties.

Change-Id: I8f6881fc106edf995814fa16218f680757be079f
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
2 files changed
tree: ed07345e4c91a610551e925b76de1c4f753f8179
  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.