Upstream fork of ATF with a couple of rk3399 patches to remove HDCP blob and increase BAUD_RATE.
Go to file
Yann Gautier a0e972438b fix(stm32mp1-fdts): remove mmc1 alias if not needed
If a board declares an mmc1 alias in its DT and is compiled without flags
STM32MP_EMMC or STM32MP_SDMMC, the DT will fail to build.
Add /delete-property/ mmc1; to correct this.

Signed-off-by: Yann Gautier <yann.gautier@st.com>
Change-Id: I1938ff99dc3d883f9174ee886f9ffa195ec60373
2022-01-28 11:26:52 +01:00
.husky build(hooks): add commitlint hook 2021-04-19 14:06:25 +01:00
bl1 refactor(measured-boot): avoid Measured-Boot dependency on Trusted-Boot 2022-01-11 23:06:22 +00:00
bl2 refactor(measured-boot): avoid Measured-Boot dependency on Trusted-Boot 2022-01-11 23:06:22 +00:00
bl2u Avoid the use of linker *_SIZE__ macros 2021-04-21 15:05:57 +02:00
bl31 feat(sme): enable SME functionality 2021-11-12 10:38:00 -06:00
bl32 fix: use correct printf format for uint64_t 2021-11-12 13:02:02 +00:00
common refactor(measured-boot): avoid Measured-Boot dependency on Trusted-Boot 2022-01-11 23:06:22 +00:00
docs feat(fwu): add platform hook for getting the boot index 2022-01-27 18:09:02 +05:30
drivers Merge "fix(nxp-drivers): ddr: corrects mapping of HNFs nodes" into integration 2022-01-27 23:05:51 +01:00
fdts fix(stm32mp1-fdts): remove mmc1 alias if not needed 2022-01-28 11:26:52 +01:00
include refactor(st-clock): update STGEN management 2022-01-27 18:06:36 +01:00
lib fix(errata): workaround for Rainier erratum 1868343 2022-01-05 17:16:19 +00:00
licenses docs(license): rectify `arm-gic.h` license 2021-04-26 12:36:00 +01:00
make_helpers fix(sve): disable ENABLE_SVE_FOR_NS for AARCH32 2021-12-22 14:03:19 +01:00
plat refactor(stm32mp1): remove unused refcount helper functions 2022-01-27 18:06:36 +01:00
services Merge "fix(trp): Distinguish between cold and warm boot" into integration 2021-12-22 21:13:03 +01:00
tools chore(npm): update package versions/license 2022-01-10 14:53:07 +00:00
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch 2019-07-12 11:06:24 +01:00
.commitlintrc.js refactor(hooks): replace cz-conventional-changelog with cz-commitlint 2022-01-24 12:55:00 +00:00
.cz.json refactor(hooks): replace cz-conventional-changelog with cz-commitlint 2022-01-24 12:55:00 +00:00
.editorconfig .editorconfig: set max line length to 100 2020-12-03 15:39:23 +00:00
.gitignore build(hooks): add Husky configuration 2021-04-19 14:06:25 +01:00
.gitreview Specify integration as the default branch for git-review 2020-04-02 07:57:17 +00:00
.versionrc.js docs(changelog): fix broken version bumping 2022-01-24 12:55:34 +00:00
Makefile refactor(measured-boot): avoid Measured-Boot dependency on Trusted-Boot 2022-01-11 23:06:22 +00:00
changelog.yaml build(changelog): add a valid scope for partition code 2022-01-27 18:09:02 +05:30
dco.txt Drop requirement for CLA in contribution.md 2016-09-27 21:52:03 +01:00
license.rst doc: De-duplicate readme and license files 2019-10-08 16:36:15 +00:00
package-lock.json build(npm): mandate Node.js engine version 2022-01-24 12:55:34 +00:00
package.json build(npm): mandate Node.js engine version 2022-01-24 12:55:34 +00:00
readme.rst doc: Formatting fixes for readme.rst 2019-10-09 15:37:59 +00:00

readme.rst

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> </head>

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:

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.

</html>