Upstream fork of ATF with a couple of rk3399 patches to remove HDCP blob and increase BAUD_RATE.
Go to file
Madhukar Pappireddy 4682461ded fconf: Extract topology node properties from HW_CONFIG dtb
Create, register( and implicitly invoke) fconf_populate_topology()
function which extracts the topology related properties from dtb into
the newly created fconf based configuration structure 'soc_topology'.
Appropriate libfdt APIs are added to jmptbl.i file for use with USE_ROMLIB
build feature.

A new property which describes the power domain levels is added to the
HW_CONFIG device tree source files.

This patch also fixes a minor bug in the common device tree file
fvp-base-gicv3-psci-dynamiq-common.dtsi
As this file includes fvp-base-gicv3-psci-common.dtsi, it is necessary
to delete all previous cluster node definitons because DynamIQ based
models have upto 8 CPUs in each cluster. If not deleted, the final dts
would have an inaccurate description of SoC topology, i.e., cluster0
with 8 or more core nodes and cluster1 with 4 core nodes.

Change-Id: I9eb406da3ba4732008a66c01afec7c9fa8ef59bf
Signed-off-by: Madhukar Pappireddy <madhukar.pappireddy@arm.com>
2020-03-11 11:25:10 -05:00
bl1 aarch32: stop speculative execution past exception returns 2020-03-01 06:44:30 -06:00
bl2 aarch32: stop speculative execution past exception returns 2020-03-01 06:44:30 -06:00
bl2u Reduce space lost to object alignment 2019-12-04 02:59:30 -06:00
bl31 fconf: necessary modifications to support fconf in BL31 & SP_MIN 2020-03-11 11:24:55 -05:00
bl32 fconf: necessary modifications to support fconf in BL31 & SP_MIN 2020-03-11 11:24:55 -05:00
common Merge changes from topic "lm/fconf" into integration 2020-02-11 16:15:45 +00:00
docs fconf: necessary modifications to support fconf in BL31 & SP_MIN 2020-03-11 11:24:55 -05:00
drivers Merge "Necessary fix in drivers to upgrade to mbedtls-2.18.0" into integration 2020-03-10 18:25:02 +00:00
fdts fconf: Extract topology node properties from HW_CONFIG dtb 2020-03-11 11:25:10 -05:00
include fconf: necessary modifications to support fconf in BL31 & SP_MIN 2020-03-11 11:24:55 -05:00
lib fconf: enhancements to firmware configuration framework 2020-03-11 10:19:21 -05:00
make_helpers Merge changes from topic "sb/dualroot" into integration 2020-03-10 13:47:47 +00:00
plat fconf: Extract topology node properties from HW_CONFIG dtb 2020-03-11 11:25:10 -05:00
services SPMD: add command line parameter to run SPM at S-EL2 or S-EL1 2020-03-03 11:38:36 +00:00
tools Merge changes from topic "sb/dualroot" into integration 2020-03-10 13:47:47 +00:00
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch 2019-07-12 11:06:24 +01:00
.editorconfig doc: Final, pre-release fixes and updates 2019-10-22 13:15:02 +00:00
.gitignore Ignore the ctags file 2020-01-22 16:08:27 +00:00
Makefile fconf: necessary modifications to support fconf in BL31 & SP_MIN 2020-03-11 11:24:55 -05:00
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
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>