da6e654bc8
The patch does below things. 1. As per current implementation, when Linux send a request to ATF to get the version of APIs which are implemented in ATF then ATF wasn't returning any version because there is a check for LIBPM module id. The ATF is used to return version for the APIs which are implemented in the firmware only. Hence moved this switch-case before checking module id to get ATF version. Also, no need to pass Linux request to the firmware for the APIs which are implemented in ATF instead return success after updating version. 2. As per current implementation, higher 16-bit is used for ATF version and lower 16-bit is used for firmware version. Now, removed 16-bit shift operation and send complete word i.e. 32-bit to Linux user as there is no user who checks ATF version. 3. Add bit mask support in the feature check PM EEMI API for QUERY and IOCTL ids. Change-Id: Icdca3de6659f3b673b81a423ed79a3c20b678768 Signed-off-by: Ronak Jain <ronak.jain@xilinx.com> Signed-off-by: Tanmay Shah <tanmay.shah@xilinx.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.