510dc79c85
There are plans to contribute a generic MHU driver to the TF-A code base in the short term. In preparation for this, rename the Corstone-700 MHU driver source files and prefix them with the name of the platform to avoid any ambiguity or name clashes with the upcoming generic MHU driver. Also rename the header guard accordingly. This renaming is inline with other platform-specific MHU drivers, such as the ones used on Broadcom [1], Socionext [2] or Amlogic [3] platforms. [1] plat/brcm/common/brcm_mhu.h [2] plat/socionext/synquacer/drivers/mhu/sq_mhu.h [3] plat/amlogic/common/aml_mhu.c Change-Id: I8a5e5b16e7c19bf931a90422dfca8f6a2a0663b4 Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com> |
||
|---|---|---|
| .husky | ||
| bl1 | ||
| bl2 | ||
| bl2u | ||
| bl31 | ||
| bl32 | ||
| common | ||
| docs | ||
| drivers | ||
| fdts | ||
| include | ||
| lib | ||
| licenses | ||
| make_helpers | ||
| plat | ||
| services | ||
| tools | ||
| .checkpatch.conf | ||
| .commitlintrc.js | ||
| .cz.json | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| .versionrc.js | ||
| Makefile | ||
| changelog.yaml | ||
| dco.txt | ||
| license.rst | ||
| package-lock.json | ||
| package.json | ||
| readme.rst | ||
readme.rst
Trusted Firmware-A
Trusted Firmware-A (TF-A) is a reference implementation of secure world software for Arm A-Profile architectures (Armv8-A and Armv7-A), including an Exception Level 3 (EL3) Secure Monitor. It provides a suitable starting point for productization of secure world boot and runtime firmware, in either the AArch32 or AArch64 execution states.
TF-A implements Arm interface standards, including:
- Power State Coordination Interface (PSCI)
- Trusted Board Boot Requirements CLIENT (TBBR-CLIENT)
- SMC Calling Convention
- System Control and Management Interface (SCMI)
- Software Delegated Exception Interface (SDEI)
The code is designed to be portable and reusable across hardware platforms and software models that are based on the Armv8-A and Armv7-A architectures.
In collaboration with interested parties, we will continue to enhance TF-A with reference implementations of Arm standards to benefit developers working with Armv7-A and Armv8-A TrustZone technology.
Users are encouraged to do their own security validation, including penetration testing, on any secure world code derived from TF-A.
More Info and Documentation
To find out more about Trusted Firmware-A, please view the full documentation that is available through trustedfirmware.org.
Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.