Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-libhei / 8deb09054137d5047cde74b8c3cd66d31d8f34bf
commit8deb09054137d5047cde74b8c3cd66d31d8f34bf[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Mon Oct 14 15:52:27 2019 -0500
committerZane Shelley <zshelle@us.ibm.com>Wed Oct 16 01:33:54 2019 +0000
tree6bf46f12ebb4cebb35a23d915a45d51e3985af54
parent65ed96a8bd8d9f47c2f4ce63bb8252115197ec05 [diff]
Create SCOM and ID SCOM register classes

SCOM and ID SCOM registers are specialized register that will exist
under the HardwareRegister abstract class.

Change-Id: I40c39536ca7321c9ef36347cef2320cf7fc4da49
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
4 files changed
tree: 6bf46f12ebb4cebb35a23d915a45d51e3985af54
  1. src/
  2. test/
  3. .gitignore
  4. LICENSE
  5. MAINTAINERS
  6. meson.build
  7. meson_options.txt
  8. README.md
README.md

openpower-libhei: Hardware Error Isolation for POWER Systems

This library is a common, portable code base for isolating errors reported by hardware registers on POWER Systems chips.

The primary consumers (and requirements drivers) will be:

Core API

See the primary API definitions for details on how to use this library.

Integration

This library is intended to be integrated into containing user applications as a set of source files (either imported, or as a git subtree/submodule).

Details TBD.

User Application Requirements and APIs

  • The method to access hardware register data will vary per user application. Therefore, this library will declare the hardware access user APIs, but each containing user application must implement the APIs for their own environment.
  • This library will not contain data regarding hardware specific information. Instead, that information will be provided by the user application in the form of the Chip Data Files.
  • Tracing, or logging, methods will vary per user application. Specifically, FSP and Hostboot firmware utilize specialized macros as a mechanism to save code image space. Therefore, the user application will need to provide a specific header file that defines these macros. Details are in the common includes header.
  • Methods to assert programming bugs will vary per user application. Therefore, much like tracing, the user application will need to provide a specific header file that defines macros for assertion. Details are included in the common includes header.

Environment configuration

  • __HEI_READ_ONLY: When defined, it will ensure any hardware write support is disabled. Note that the Chip Data Files will contain rules for clearing and masking register bits. Both of which will require modifying hardware registers, which is not allowed by user applications like OpenBMC or FSP firmware.

Development Notes

  • The Hostboot and FSP environments only support up to C++11. Therefore, this library cannot use anything newer at this time.
  • Hostboot has a very limited environment. It does not include libc or libstdc++. However, Hostboot has implemented select functions from those libraries as needed. For details, you can reference src/include/ in the POWER Systems Hostboot firmware.