Upstream fork of ATF with a couple of rk3399 patches to remove HDCP blob and increase BAUD_RATE.
Go to file
Jeremy Linton ab061eb732 rpi4: SMCCC PCI implementation
The rpi4 has a single nonstandard ECAM. It is broken
into two pieces, the root port registers, and a window
to a single device's config space which can be moved
between devices. Now that we have widened the page
tables/MMIO window, we can create a read/write acces
functions that are called by the SMCCC/PCI API.

As an example platform, the rpi4 single device ECAM
region quirk is pretty straightforward. The assumption
here is that a lower level (uefi) has configured and
initialized the PCI root to match the values we are
using here.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
Change-Id: Ie1ffa8fe9aa1d3c62e6aa84746a949c1009162e0
2021-07-28 09:41:55 +02:00
.husky build(hooks): add commitlint hook 2021-04-19 14:06:25 +01:00
bl1 Add PIE support for AARCH32 2021-04-21 15:05:57 +02:00
bl2 Add PIE support for AARCH32 2021-04-21 15:05:57 +02:00
bl2u Avoid the use of linker *_SIZE__ macros 2021-04-21 15:05:57 +02:00
bl31 SMCCC/PCI: Handle std svc boilerplate 2021-05-25 14:49:08 +02:00
bl32 Add PIE support for AARCH32 2021-04-21 15:05:57 +02:00
common fix(fdt): fix OOB write in uuid parsing function 2021-07-26 16:42:25 +01:00
docs Merge "docs(maintainers): update imx8 entry" into integration 2021-07-25 15:02:03 +02:00
drivers fix(drivers/scmi-msg): entry: add weak functions 2021-07-22 10:27:48 +08:00
fdts Merge changes from topic "tc0_tfa_v25" into integration 2021-06-30 12:06:13 +02:00
include Merge changes from topic "allwinner_mmap" into integration 2021-07-26 17:29:30 +02:00
lib fix(el3_runtime): fix SVE and AMU extension enablement flags 2021-07-23 10:33:59 +01:00
licenses docs(license): rectify `arm-gic.h` license 2021-04-26 12:36:00 +01:00
make_helpers feat(sve): enable SVE for the secure world 2021-06-28 13:24:24 +01:00
plat rpi4: SMCCC PCI implementation 2021-07-28 09:41:55 +02:00
services fix(sdei): set SPSR for SDEI based on TakeException 2021-07-23 13:20:28 +01:00
tools fix(tools/stm32image): improve the tool 2021-06-22 14:10:27 +02:00
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch 2019-07-12 11:06:24 +01:00
.cz.json build(hooks): add Commitizen hook 2021-04-19 14:06:25 +01: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
Makefile Merge changes from topic "sb/measured-boot" into integration 2021-07-05 10:19:19 +02:00
commitlint.config.js revert(commitlint): disable `signed-off-by` rule 2021-04-27 16:12:10 +01: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
package-lock.json build(hooks): bump trim-newlines from 3.0.0 to 3.0.1 2021-06-10 12:31:36 +01:00
package.json build(hooks): update Commitizen to ^4.2.4 2021-05-12 15:43:56 +01: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>