Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 2e6c6f7357fe823b8af0292568fc74645f21b942
commit2e6c6f7357fe823b8af0292568fc74645f21b942[log] [tgz]
authorAlpana Kumari <alpankum@in.ibm.com>Thu Dec 03 00:10:03 2020 -0600
committerSantosh Puranik <santosh.puranik@in.ibm.com>Mon Feb 21 09:54:40 2022 +0000
tree6a3f0d5d185e7638d51f57d512832b853dc0701c
parent187bc274184969959dfb3f337bbb13eb9ea6d387 [diff]
Read the PCIe Cable card's presence GPIO

Take pre and post action based on it's presence on PASS2 planar.
Smae action on PASS1 planar will be independent of presence.
If presence GPIO says it is Present then enable the output line.

Test-
DBG: Processing - /sys/bus/i2c/drivers/at24/20-0050/eeprom, for presence Node
DBG:presPinName-SLOT0_EXPANDER_PRSNT_N
DBG:presenceLine INPUT request done

DBG:Device not attached, but forcing to take action

DBG:preAction executing...
Setting GPIO: SLOT0_PRSNT_EN_RSVD to 1
DBG: Output pin Updated

Binding device 20-0050
echo "20-0050" > /sys/bus/i2c/drivers/at24/bind
sh: line 1: echo: write error: No such device
EEPROM /sys/bus/i2c/drivers/at24/20-0050/eeprom does not exist. Take failure action
Setting GPIO: SLOT0_PRSNT_EN_RSVD to 0

Tested on rain104bmc-
pin - SLOT0_EXPANDER_PRSNT_N
value - 0
presence pin state is- 0,i.e. it is present.
Setting output GPIO: SLOT0_PRSNT_EN_RSVD to 1

Change-Id: I055cb3598358fb36ad4fd986b5d96ff7aaccda73
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
1 file changed
tree: 6a3f0d5d185e7638d51f57d512832b853dc0701c
  1. examples/
  2. subprojects/
  3. test/
  4. vpd-manager/
  5. vpd-parser/
  6. vpdecc/
  7. .clang-format
  8. .gitignore
  9. app.cpp
  10. args.cpp
  11. args.hpp
  12. common_utility.cpp
  13. common_utility.hpp
  14. const.hpp
  15. defines.hpp
  16. extra-properties-example.yaml
  17. extra-properties.mako.hpp
  18. extra-properties.py
  19. ibm_vpd_app.cpp
  20. ibm_vpd_utils.cpp
  21. ibm_vpd_utils.hpp
  22. impl.cpp
  23. impl.hpp
  24. LICENSE
  25. MAINTAINERS
  26. meson.build
  27. meson_options.txt
  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.