| /trusted-firmware-a/docs/components/spd/ |
| A D | optee-dispatcher.rst | 4 `OP-TEE OS`_ is a Trusted OS running as Secure EL1.
13 .. _OP-TEE OS: https://github.com/OP-TEE/build
|
| A D | tlk-dispatcher.rst | 20 TLK is a Trusted OS running as Secure EL1. It is a Free Open Source Software
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/spd/ |
| A D | optee-dispatcher.rst.txt | 4 `OP-TEE OS`_ is a Trusted OS running as Secure EL1.
13 .. _OP-TEE OS: https://github.com/OP-TEE/build
|
| A D | tlk-dispatcher.rst.txt | 20 TLK is a Trusted OS running as Secure EL1. It is a Free Open Source Software
|
| /trusted-firmware-a/make_helpers/ |
| A D | build_env.mk | 43 ifdef OS
44 ifneq ($(findstring ${OS}, Windows_NT),)
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/about/ |
| A D | features.rst.txt | 35 for example an AArch32 Secure OS.
42 When a Secure-EL1 Payload (SP) is present, for example a Secure OS, the
49 - SPDs for the `OP-TEE Secure OS`_, `NVIDIA Trusted Little Kernel`_
50 and `Trusty Secure OS`_.
121 .. _OP-TEE Secure OS: https://github.com/OP-TEE/optee_os
123 .. _Trusty Secure OS: https://source.android.com/security/trusty
|
| /trusted-firmware-a/docs/about/ |
| A D | features.rst | 35 for example an AArch32 Secure OS.
42 When a Secure-EL1 Payload (SP) is present, for example a Secure OS, the
49 - SPDs for the `OP-TEE Secure OS`_, `NVIDIA Trusted Little Kernel`_
50 and `Trusty Secure OS`_.
121 .. _OP-TEE Secure OS: https://github.com/OP-TEE/optee_os
123 .. _Trusty Secure OS: https://source.android.com/security/trusty
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/ |
| A D | allwinner.rst.txt | 92 Trusted OS dispatcher
95 One can boot Trusted OS(OP-TEE OS, bl32 image) along side bl31 image on Allwinner A64.
98 while compiling the bl31 image and make sure the loader (SPL) loads the Trusted OS binary to
|
| A D | nvidia-tegra.rst.txt | 74 Trusted OS dispatcher
77 Tegra supports multiple Trusted OS'.
84 This allows other Trusted OS vendors to use the upstream code and include
87 These are the supported Trusted OS' by Tegra platforms.
118 size for loading the Trusted OS and the UART port ID to be used. The Tegra
|
| A D | ls1043a.rst.txt | 43 --> BL32(Tee OS) --> TF-A BL31 --> BL33(u-boot) --> Linux kernel
|
| /trusted-firmware-a/docs/plat/ |
| A D | allwinner.rst | 92 Trusted OS dispatcher
95 One can boot Trusted OS(OP-TEE OS, bl32 image) along side bl31 image on Allwinner A64.
98 while compiling the bl31 image and make sure the loader (SPL) loads the Trusted OS binary to
|
| A D | nvidia-tegra.rst | 74 Trusted OS dispatcher
77 Tegra supports multiple Trusted OS'.
84 This allows other Trusted OS vendors to use the upstream code and include
87 These are the supported Trusted OS' by Tegra platforms.
118 size for loading the Trusted OS and the UART port ID to be used. The Tegra
|
| A D | ls1043a.rst | 43 --> BL32(Tee OS) --> TF-A BL31 --> BL33(u-boot) --> Linux kernel
|
| /trusted-firmware-a/lib/zlib/ |
| A D | inflate.h | 24 OS, /* i: waiting for extra flags and operating system (gzip) */ enumerator
|
| /trusted-firmware-a/plat/arm/board/fvp/fdts/ |
| A D | fvp_fw_config.dts | 39 /* If required, SPD should enable loading of trusted OS fw config */
|
| /trusted-firmware-a/docs/security_advisories/ |
| A D | security-advisory-tfv-6.rst | 57 Note that if other privileged software, for example a Rich OS kernel, implements
117 integrated, for example as part of a Trusted OS. Therefore any Variant 2
133 applicable for TF. However, Secure Payloads (for example, Trusted OS) should
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/security_advisories/ |
| A D | security-advisory-tfv-6.rst.txt | 57 Note that if other privileged software, for example a Rich OS kernel, implements
117 integrated, for example as part of a Trusted OS. Therefore any Variant 2
133 applicable for TF. However, Secure Payloads (for example, Trusted OS) should
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | rt-svc-writers-guide.rst.txt | 22 Arm to support `PSCI`_, Secure Monitor for a Trusted OS and SoC specific
42 reserved exclusively for Trusted OS providers or for interoperability with
55 Fast 50-63 Trusted OS calls
58 Yielding 2-63 Trusted OS Standard Calls
305 Services that handle SMC Functions targeting a Trusted OS, Trusted Application,
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | rt-svc-writers-guide.rst | 22 Arm to support `PSCI`_, Secure Monitor for a Trusted OS and SoC specific
42 reserved exclusively for Trusted OS providers or for interoperability with
55 Fast 50-63 Trusted OS calls
58 Yielding 2-63 Trusted OS Standard Calls
305 Services that handle SMC Functions targeting a Trusted OS, Trusted Application,
|
| /trusted-firmware-a/docs/components/ |
| A D | secure-partition-manager.rst | 103 NWd (Hypervisor or OS kernel) to SPMC located either at S-EL1 or S-EL2.
612 deployed in NWd, the Hypervisor or OS kernel must invoke the interface
697 - Hypervisor or OS kernel in NS-EL1/EL2: the SPMD returns the SPMC version
711 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
726 caller, either it being the Hypervisor or OS kernel, as well as a secure
735 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
789 - An SP cannot send a direct request to an Hypervisor or OS kernel.
790 - An Hypervisor or OS kernel can send a direct request to an SP.
791 - An SP can send a direct response to an Hypervisor or OS kernel.
852 The Hypervisor or OS kernel can issue an FFA_SPM_ID_GET call handled by the
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | secure-partition-manager.rst.txt | 103 NWd (Hypervisor or OS kernel) to SPMC located either at S-EL1 or S-EL2.
612 deployed in NWd, the Hypervisor or OS kernel must invoke the interface
697 - Hypervisor or OS kernel in NS-EL1/EL2: the SPMD returns the SPMC version
711 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
726 caller, either it being the Hypervisor or OS kernel, as well as a secure
735 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
789 - An SP cannot send a direct request to an Hypervisor or OS kernel.
790 - An Hypervisor or OS kernel can send a direct request to an SP.
791 - An SP can send a direct response to an Hypervisor or OS kernel.
852 The Hypervisor or OS kernel can issue an FFA_SPM_ID_GET call handled by the
[all …]
|
| /trusted-firmware-a/docs/plat/marvell/armada/ |
| A D | build.rst | 97 by Trusted OS (OP-TEE OS, BL32). The TF-A only prepares CCU address translation windows
99 When Trusted OS activates LLC SRAM, the CCU window target is changed to SRAM.
100 There is no reason to enable this feature if OP-TEE OS built with CFG_WITH_PAGER=n.
101 Only set LLC_SRAM=1 if OP-TEE OS is built with CFG_WITH_PAGER=y.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/marvell/armada/ |
| A D | build.rst.txt | 97 by Trusted OS (OP-TEE OS, BL32). The TF-A only prepares CCU address translation windows
99 When Trusted OS activates LLC SRAM, the CCU window target is changed to SRAM.
100 There is no reason to enable this feature if OP-TEE OS built with CFG_WITH_PAGER=n.
101 Only set LLC_SRAM=1 if OP-TEE OS is built with CFG_WITH_PAGER=y.
|
| /trusted-firmware-a/docs/plat/nxp/ |
| A D | nxp-layerscape.rst | 72 + EL1 BL32(Tee OS) | kernel
88 + EL1 fip-ddr BL32(Tee OS) | kernel
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/nxp/ |
| A D | nxp-layerscape.rst.txt | 72 + EL1 BL32(Tee OS) | kernel
88 + EL1 fip-ddr BL32(Tee OS) | kernel
|