Tegra194: memctrl: force viw and vifalr/w transactions as non-coherent
Krishna Reddy authored
Force memory transactions from viw and viflar/w as non-coherent from
no-override. This is necessary as iso clients shouldn't use coherent
path and stage-2 smmu mappings won't mark transactions as non-coherent.
For native case, no-override works. But, not for virtualization case.

Change-Id: I1a8fc17787c8d0f8579bdaeeb719084993e27276
Signed-off-by: default avatarKrishna Reddy <vdumpa@nvidia.com>
221b8e57
Name Last commit Last update
bl1 Merge "PIE: make call to GDT relocation fixup generalized" into integration
bl2 Merge "PIE: make call to GDT relocation fixup generalized" into integration
bl2u Reduce space lost to object alignment
bl31 bl31: Split into two separate memory regions
bl32 pmf: Make the runtime instrumentation work on AArch32
common Refactor load_auth_image_internal().
docs Merge "docs: Creating a Change Log Template File" into integration
drivers Merge "console: 16550: Prepare for skipping initialisation" into integration
fdts A5DS: Correct system freq, Cache Writeback Granule
include Merge "a8k: Implement platform specific power off" into integration
lib Unify type of "cpu_idx" across PSCI module.
make_helpers bl31: Split into two separate memory regions
plat Tegra194: memctrl: force viw and vifalr/w transactions as non-coherent
services spm-mm: Rename aarch64 assembly files
tools tools: Add show_memory script
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch
.editorconfig doc: Final, pre-release fixes and updates
.gitignore meson: Rename platform directory to amlogic
Makefile bl31: Split into two separate memory regions
dco.txt Drop requirement for CLA in contribution.md
license.rst doc: De-duplicate readme and license files
readme.rst doc: Formatting fixes for 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:

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.