Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 9654e034b6eda21e64aebb1802f6a13661924681
commit9654e034b6eda21e64aebb1802f6a13661924681[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Wed Sep 17 17:18:42 2025 +0000
committerSunnySrivastava <sunnsr25@in.ibm.com>Fri Sep 19 04:31:50 2025 +0000
tree2ccdc9d9e49579d4f205c4e1de9295db38c1d832
parent0d63123e34fb97ed35332a0cd874079bdc121844 [diff]
Check for empty interface property pair

This commit adds check for empty interface property pair before
processing it. In some patch sets CI is complaining for the check, hence
it has been added.

Test:
```
- Do vpd-tool writeKeyword operation on /system/chassis/motherboard's
  VINI record PN keyword
- Observe the write operation is successful and
  /system/chassis's Decorator.Asset PartNumber property is also updated
  with the same value
```

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