No description
Find a file
Chris Kay 8620bd0b93 build: use toolchain identifiers in conditions
The toolchain refactor change introduces the `${toolchain}-${tool}-id`
variables, which provide identifiers for all of the toolchain tools used
by the build system. This change replaces the various conditions that
are in use to identify these tools based on the path with a standard set
of comparisons against these new identifier variables.

Change-Id: Ib60e592359fa6e415c19a012e68d660f87436ca7
Signed-off-by: Chris Kay <chris.kay@arm.com>
2024-02-06 11:14:52 +00:00
.husky style(hooks): copyright year check as per author email 2024-01-19 14:29:29 +01:00
bl1 build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl2 build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl2u build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl31 build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl32 build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
common feat(cpufeat): add feature detection for FEAT_CSV2_3 2024-01-29 14:06:56 +00:00
docs Merge "docs(contributing): various improvements" into integration 2024-02-02 13:54:12 +01:00
drivers Merge changes from topic "st-bsec3" into integration 2024-01-29 16:38:43 +01:00
fdts Merge changes from topic "st-bsec-otp" into integration 2024-01-23 12:54:09 +01:00
include Merge "feat(spmd): initialize SCR_EL3.EEL2 bit at RESET" into integration 2024-02-03 11:29:39 +01:00
lib build: use new toolchain variables for tools 2024-02-06 11:14:52 +00:00
licenses docs(license): rectify arm-gic.h license 2021-04-26 12:36:00 +01:00
make_helpers build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
plat build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
services build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
tools build: use new toolchain variables for tools 2024-02-06 11:14:52 +00:00
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch 2019-07-12 11:06:24 +01:00
.commitlintrc.js build(commitlint): make the scope optional 2022-05-03 11:06:50 +02: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 fix: .gitignore to include memory tools 2023-08-11 11:49:53 +01:00
.gitreview Specify integration as the default branch for git-review 2020-04-02 07:57:17 +00:00
.nvmrc build(npm): add NVM version file 2022-10-10 13:24:22 +01:00
.readthedocs.yaml fix: use rsvg-convert as the conversion backend 2023-07-28 12:37:49 +01:00
.versionrc.js feat(build): manage patch version in Makefile 2023-10-04 16:34:38 +02:00
changelog.yaml Merge changes from topics "rcar-tools-fix", "toolchain-cleanup" into integration 2024-01-24 16:11:22 +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
Makefile build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
package-lock.json docs(changelog): changelog for v2.10 release 2023-11-22 11:52:02 +00:00
package.json docs(changelog): changelog for v2.10 release 2023-11-22 11:52:02 +00:00
poetry.lock build(poetry): bump requests from 2.30.0 to 2.31.0 2023-09-06 14:51:49 +00:00
pyproject.toml docs(changelog): changelog for v2.10 release 2023-11-22 11:52:02 +00:00
readme.rst doc: Formatting fixes for readme.rst 2019-10-09 15:37:59 +00:00

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.*

.. _Armv7-A and Armv8-A: https://developer.arm.com/products/architecture/a-profile
.. _Secure Monitor: http://www.arm.com/products/processors/technologies/trustzone/tee-smc.php
.. _Power State Coordination Interface (PSCI): PSCI_
.. _PSCI: http://infocenter.arm.com/help/topic/com.arm.doc.den0022d/Power_State_Coordination_Interface_PDD_v1_1_DEN0022D.pdf
.. _Trusted Board Boot Requirements CLIENT (TBBR-CLIENT): https://developer.arm.com/docs/den0006/latest/trusted-board-boot-requirements-client-tbbr-client-armv8-a
.. _SMC Calling Convention: http://infocenter.arm.com/help/topic/com.arm.doc.den0028b/ARM_DEN0028B_SMC_Calling_Convention.pdf
.. _System Control and Management Interface (SCMI): SCMI_
.. _SCMI: http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/DEN0056A_System_Control_and_Management_Interface.pdf
.. _Software Delegated Exception Interface (SDEI): SDEI_
.. _SDEI: http://infocenter.arm.com/help/topic/com.arm.doc.den0054a/ARM_DEN0054A_Software_Delegated_Exception_Interface.pdf
.. _Arm A-Profile architectures: https://developer.arm.com/architectures/cpu-architecture/a-profile
.. _view the full documentation: https://www.trustedfirmware.org/docs/tf-a
.. _trustedfirmware.org: http://www.trustedfirmware.org