Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 0dba14da4a4580594e33ba72d596a1a0629d345f
commit0dba14da4a4580594e33ba72d596a1a0629d345f[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Wed Jun 25 03:39:38 2025 -0500
committerSouvik Roy <souvikroyofficial10@gmail.com>Thu Jul 10 08:00:00 2025 -0500
tree9536933b6de3c2626b8015baedd509ac6a1a0290
parent14773e8f1a19d124f4ca87f4e09d0a49e647db0e [diff]
Listener: Register correlated properties callback

This commit implements API to register callback for all interfaces in
correlated_properties.json.

```
Test:
1. Patch debug traces in the callback function.
2. On rainier 2s2u simics, do a busctl set-property on Decorator.Asset
   PartNumber, com.ibm.ipzvpd.VINI PN of LCD Op Panel.
3. Observe vpd-manager logs and observe traces indicating callback is
   getting triggered for above property changes.
```

Change-Id: I1ca2ae65724d8aa27424775fb1290a4139518644
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
3 files changed
tree: 9536933b6de3c2626b8015baedd509ac6a1a0290
  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.