commit | 8589375ff66d10295d609cca53cdf2f9f12a5472 | [log] [tgz] |
---|---|---|
author | Santosh Puranik <santosh.puranik@in.ibm.com> | Tue Nov 10 21:31:43 2020 +0530 |
committer | Santosh Puranik <santosh.puranik@in.ibm.com> | Fri Dec 11 23:02:45 2020 +0530 |
tree | e41a5feb8c8a4cd9fb61fb4184deb93de2b68723 | |
parent | 4641bff5ac73e0ba3b91b9375096fe8f123ddc68 [diff] |
ibm-read-vpd: Enable skipping VPD read if host is powered ON This commit keys off of a JSON attribute on the FRU that enables the parser code to skip reading VPD when the host is powered ON. On IBM systems, certain FRU VPD is inaccessible to the BMC when the host is powered ON. This commit enables us to skip such FRUs. It relies on the xyz.openbmc_project.State.Chassis.CurrentPowerState property to determine the host power state. Tested: Tested on Rainier simulation model by manually setting the above property and ensuring that VPD reads are skipped if the FRU contains the "powerOffOnly" key in the JSON. Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: Iaa55d32f7b3641fa0fd41dbd79620dbff2b1673a
#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:
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 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.
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:
#
and are > 255 bytes in length).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.