Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-libhei / 23244cb7c3d8f26844f31cdb9041c1137fef3457
commit23244cb7c3d8f26844f31cdb9041c1137fef3457[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Fri Aug 30 21:12:12 2019 -0500
committerZane Shelley <zshelle@us.ibm.com>Fri Sep 13 21:49:53 2019 -0500
tree96b2ce7194ace3bee6db02fbaa3f7ed3420eba77
parent701fcc1c06b91153828a577cf5f72f6f38853f09 [diff]
Renamed SCAN_COMM_REGISTER_CLASS to Register

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: Ida0c807af6b908c88519a6671642f7a5dce8f6cd
10 files changed
tree: 96b2ce7194ace3bee6db02fbaa3f7ed3420eba77
  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 included in the user APIs.
  • 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 user APIs.

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.