summaryrefslogtreecommitdiffstats
path: root/extensions/openpower-pels/pel_types.hpp
Commit message (Collapse)AuthorAgeFilesLines
* PEL: Add enums for transmission statesMatt Spinler2019-12-091-0/+11
| | | | | | | | | | So far, the states are new, sent, and acked. Also added PEL object access to getting and setting these on the User Header section object. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I0dfb2d1a39fe69b2a47bf7d461f08e92039a3e03
* PEL: Validate the Action Flags fieldMatt Spinler2019-11-081-1/+23
| | | | | | | | | | | | | | | | According to the PEL spec, the Action Flags and Event Type fields in the User Header section must be in agreement with the Severity field. So, when a PEL is being created from an OpenBMC event log, check those values for correctness and fix them up if required. In addition, as those fields are optional in the message registry, this code will also just set these two fields to valid values if they were left out. The rules being followed are documented in the PEL readme. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
* PEL: Move severity type enums to a headerMatt Spinler2019-11-041-0/+15
| | | | | | | Move them to a header file so other files can use them in the future. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Icb604489e9629724a79d2fc8b110e461b6aa6e01
* PEL: Create UserHeader from parametersMatt Spinler2019-10-091-0/+16
| | | | | | | | | | | Add a constructor to the UserHeader section class so it can be built from the message registry entry for that error along with the event log severity. This will be used when creating PELs from OpenBMC event logs. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I7e432f59de7b3f0ba77c3e5887ed5ec3f442ed44
* PEL: Create PrivateHeader from parametersMatt Spinler2019-10-091-0/+25
| | | | | | | | | | Add a constructor to the PrivateHeader class so it can be built from the creator's component ID, the OpenBMC log ID, and the creation timestamp. This will be used when creating PELs from OpenBMC event logs. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I2d1217b9ff0317195366bee50fa72953fd5341dc
* PEL: Read SRC fields out of the registryMatt Spinler2019-10-091-0/+6
| | | | | | | | The SRC (System Reference code) is a section in the PEL and several of its fields are sourced from the message registry. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I4ca7d18a8225f2667b762015c6fd74bfb59d70ff
* PEL: Add FailingMTMS PEL section classMatt Spinler2019-09-271-0/+5
| | | | | | | | | | | | | This PEL section contains the Machine Type-Model and Serial number of the enclosure and is required for BMC PELs. In the constructor that creates the section from scratch, it gets those values from the DataInterface class. This commit doesn't hook this section into the PEL class as there are some prerequisites that still need to be done first. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I24d679b57751afb00539691defef180191ea8fc7
* PEL: Move PEL section IDs into a header fileMatt Spinler2019-09-271-0/+34
These will eventually need to be known to a piece of code that unflattens a PEL into the appropriate section class objects based on the section ID field in the PEL data. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I90b9d4be49b2e3807a620745fa663f94f7f4e62c
OpenPOWER on IntegriCloud