Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 58e22145810d6dc88d1afe60e03135e8caf198ba
commit58e22145810d6dc88d1afe60e03135e8caf198ba[log] [tgz]
authorAlpana Kumari <alpankum@in.ibm.com>Tue May 05 00:22:12 2020 -0500
committerSantosh Puranik <santosh.puranik@in.ibm.com>Mon Nov 02 11:10:02 2020 +0530
tree02837e10bfe73150ee443d2d5967fcfbf2575aee
parenta00936f8253273352e7e4453ebf11c1c9a044947 [diff]
Handling FRU and Module in vpd read code

Misc changes to handle reading of CPU VPD.

Change-Id: Ia8143dec680bbfeecb1e63505650428103192157
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
2 files changed
tree: 02837e10bfe73150ee443d2d5967fcfbf2575aee
  1. examples/
  2. test/
  3. vpd-manager/
  4. vpdecc/
  5. .clang-format
  6. .gitignore
  7. app.cpp
  8. args.cpp
  9. args.hpp
  10. const.hpp
  11. defines.hpp
  12. extra-properties-example.yaml
  13. extra-properties.mako.hpp
  14. extra-properties.py
  15. ibm_vpd_app.cpp
  16. impl.cpp
  17. impl.hpp
  18. keyword_vpd_parser.cpp
  19. keyword_vpd_parser.hpp
  20. LICENSE
  21. MAINTAINERS
  22. memory_vpd_parser.cpp
  23. memory_vpd_parser.hpp
  24. meson.build
  25. meson_options.txt
  26. parser.cpp
  27. parser.hpp
  28. README.md
  29. store.hpp
  30. types.hpp
  31. utilInterface.hpp
  32. utils.cpp
  33. utils.hpp
  34. vpd_tool.cpp
  35. vpd_tool_impl.cpp
  36. vpd_tool_impl.hpp
  37. write.cpp
  38. write.hpp
  39. writefru.mako.hpp
  40. writefru.py
  41. writefru.yaml
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 here.

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.