Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 647417a91cf16c83578c391dc3900f36a4233701
commit647417a91cf16c83578c391dc3900f36a4233701[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Wed Jul 16 08:20:06 2025 -0500
committerSouvik Roy <souvikroyofficial10@gmail.com>Mon Aug 25 15:08:34 2025 +0000
tree567e2cbdaa315a915d2de0577944c64670a3ecf0
parentb2b90bc34b2db036939c63d84b8286d3b96bb0cd [diff]
Implement get correlated properties API

This commit implements API used to get correlated properties for given
property. This API is required to process correlated properties
callback.

Test:
```
- Add debug traces to callback processing method
- On rainier 2s2u simics, do busctl set-property on /system Decorator
  Asset interface's SerialNumber property
- Observe get correlated properties API return targets:
  /xyz/openbmc_project/inventory/system com.ibm.ipzvpd.VSYS SE
  /xyz/openbmc_project/inventory/system/chassis com.ibm.ipzvpd.VSYS SE
  /xyz/openbmc_project/inventory/system/chassis/motherboard
com.ibm.ipzvpd.VSYS SE
 /xyz/openbmc_project/inventory/system/chassis/motherboard/tod_battery
com.ibm.ipzvpd.VSYS SE
- On rainier 2s2u simics, do busctl set-property on /system Decorator
  Asset's PartNumber property
- Observe get correlated properties API return target:
  /xyz/openbmc_project/inventory/system/chassis/motherboard
  com.ibm.ipzvpd.VINI PN
```

Change-Id: I3ad537f7b4f4663681a192cc137b267c114ac03a
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
1 file changed
tree: 567e2cbdaa315a915d2de0577944c64670a3ecf0
  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.