Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 2dfdbdd54aa70f6978994b871d2a9a6ca2940084
commit2dfdbdd54aa70f6978994b871d2a9a6ca2940084[log] [tgz]
authorPriyanga Ramasamy <priyanga24@in.ibm.com>Fri Aug 18 10:07:37 2023 +0000
committerJinu Joy Thomas <jinu.joy.thomas@in.ibm.com>Mon Sep 11 04:04:00 2023 +0000
treec1dce6f20d1bdf2a50f99f0cdfe67e6d0b123239
parentf98768142fb53215c5aeb312ed7525dbc9fae654 [diff]
Skip displaying asset only if VINI is not present

This commit has logic in vpd-tool to display properties under
Asset interface only if VINI properties are not required to
display. This is done to avoid duplicate entries in vpd-tool
output as the properties from Asset interface are derived from
keyowrds under VINI interface.

Test:
vpd-tool -o -O /system
[
    {
        "/system": {
            "LocationCode": "U9105.42A.13BEA10",
            "Model": "9105-42A",
            "Present": "true",
            "PrettyName": "System",
            "SerialNumber": "13BEA10",
            "SubModel": "S0",
            "TYPE": "FRU",
            "type": "xyz.openbmc_project.Inventory.Item.System"
        }
    }
]

vpd-tool -o -O /system/chassis/motherboard/fan1
[
    {
        "/system/chassis/motherboard/fan1": {
            "CC": "7B5F",
            "DR": "Blower",
            "FN": "02YK323",
            "LocationCode": "U78DB.ND0.WZS0018-A1",
            "PN": "02YK323",
            "Present": "true",
            "RI": "",
            "RT": "",
            "SN": "YL12JP1C1234",
            "TYPE": "FRU",
            "type": "xyz.openbmc_project.Inventory.Item.Fan"
        }
    }
]

Signed-off-by: Priyanga Ramasamy <priyanga24@in.ibm.com>
Change-Id: Ia9c76bd03220b7218cb5f7792100e01fc57a6131
1 file changed
tree: c1dce6f20d1bdf2a50f99f0cdfe67e6d0b123239
  1. examples/
  2. ibm_vpd/
  3. subprojects/
  4. test/
  5. vpd-manager/
  6. vpd-parser/
  7. vpdecc/
  8. .clang-format
  9. .gitignore
  10. app.cpp
  11. args.cpp
  12. args.hpp
  13. common_utility.cpp
  14. common_utility.hpp
  15. const.hpp
  16. defines.hpp
  17. extra-properties-example.yaml
  18. extra-properties.mako.hpp
  19. extra-properties.py
  20. ibm_vpd_app.cpp
  21. ibm_vpd_utils.cpp
  22. ibm_vpd_utils.hpp
  23. impl.cpp
  24. impl.hpp
  25. LICENSE
  26. meson.build
  27. meson.options
  28. OWNERS
  29. README.md
  30. store.hpp
  31. types.hpp
  32. utilInterface.hpp
  33. vpd_exceptions.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.