| /tf-a-ffa_el3_spmc/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
|
| /tf-a-ffa_el3_spmc/make_helpers/ |
| A D | build_env.mk | 43 ifdef OS
44 ifneq ($(findstring ${OS}, Windows_NT),)
|
| /tf-a-ffa_el3_spmc/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
|
| /tf-a-ffa_el3_spmc/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`_.
123 .. _OP-TEE Secure OS: https://github.com/OP-TEE/optee_os
125 .. _Trusty Secure OS: https://source.android.com/security/trusty
|
| /tf-a-ffa_el3_spmc/lib/zlib/ |
| A D | inflate.h | 24 OS, /* i: waiting for extra flags and operating system (gzip) */ enumerator
|
| A D | inflate.c | 732 state->mode = OS;
733 case OS:
|
| /tf-a-ffa_el3_spmc/plat/arm/board/fvp/fdts/ |
| A D | fvp_fw_config.dts | 39 /* If required, SPD should enable loading of trusted OS fw config */
|
| /tf-a-ffa_el3_spmc/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
|
| /tf-a-ffa_el3_spmc/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,
|
| A D | image-terminology.rst | 68 Typically this is a TEE or Trusted OS, providing runtime secure services to the
79 For example, UEFI or uboot. Its primary purpose is to boot a normal world OS.
|
| A D | initial-build.rst | 76 include other runtime services, for example Trusted OS services. A guide
|
| A D | psci-lib-integration-guide.rst | 5 integrate with a suitable Trusted OS for an Armv8-A AArch32 system. The PSCI
13 include Trusted OS functionality. A minimal AArch32 Secure Payload, SP-MIN, is
|
| A D | build-options.rst | 77 Trusted OS Extra1 image for the ``fip`` target.
80 Trusted OS Extra2 image for the ``fip`` target.
593 UEFI+ACPI this can provide a certain amount of OS forward compatibility
|
| /tf-a-ffa_el3_spmc/docs/components/ |
| A D | secure-partition-manager.rst | 103 NWd (Hypervisor or OS kernel) to SPMC located either at S-EL1 or S-EL2.
323 Secure Payload BL32 (Trusted OS): offset=0x1BCD1, size=0x15270, cmdline="--tos-fw"
470 secure partitions. For this a VM (Hypervisor or OS kernel), or SP invokes one of:
622 - Hypervisor or OS kernel in NS-EL1/EL2: the SPMD returns the SPMC version
636 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
646 When invoked from the Hypervisor or OS kernel, the buffers are mapped into the
660 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
714 - An SP cannot send a direct request to an Hypervisor or OS kernel.
715 - An Hypervisor or OS kernel can send a direct request to an SP.
716 - An SP can send a direct response to an Hypervisor or OS kernel.
[all …]
|
| A D | debugfs-design.rst | 106 the higher level OS if the latter implements its own driver for the same
|
| A D | secure-partition-manager-mm.rst | 23 phones, tablets, STBs and embedded devices, a Trusted OS instantiates trusted
26 used by Non-secure world applications to access these services. A Trusted OS
39 include a Global Platform Trusted OS. Security functions are accessed through
127 Payload image executing at S-EL1 (e.g. a Trusted OS). Both are referred to as
|
| /tf-a-ffa_el3_spmc/docs/plat/marvell/armada/ |
| A D | build.rst | 96 by Trusted OS (OP-TEE OS, BL32). The TF-A only prepares CCU address translation windows
98 When Trusted OS activates LLC SRAM, the CCU window target is changed to SRAM.
99 There is no reason to enable this feature if OP-TEE OS built with CFG_WITH_PAGER=n.
100 Only set LLC_SRAM=1 if OP-TEE OS is built with CFG_WITH_PAGER=y.
|
| /tf-a-ffa_el3_spmc/docs/ |
| A D | glossary.rst | 194 Trusted Little Kernel. A Trusted OS from NVIDIA.
|
| /tf-a-ffa_el3_spmc/docs/threat_model/ |
| A D | threat_model_spm.rst | 22 - Mutual isolation of the normal world and the secure world (e.g. a Trusted OS
135 (Hypervisor) or NS-EL1 (VM or OS kernel).
204 | | A similar component can exist in the OS kernel |
|
| A D | threat_model.rst | 58 | ``DF4`` | | Secure world software (e.g. trusted OS) interact |
62 | ``DF5`` | | Non-secure world software (e.g. rich OS) interact |
244 | | physically, through the Rich OS, or using the |
|
| /tf-a-ffa_el3_spmc/docs/process/ |
| A D | coding-guidelines.rst | 311 - BL31 Trusted OS SPD code discovers that BL2 has not loaded the corresponding
312 Trusted OS, which is critical for platform operation.
339 - A Trusted OS is waiting for a response from a proxy in the normal world that
|
| /tf-a-ffa_el3_spmc/docs/design/ |
| A D | firmware-design.rst | 91 stages and also by the Normal World Rich OS.
95 - TOS_FW_CONFIG - Trusted OS Firmware configuration file. Used by Trusted OS
860 If a system runs a Trusted OS or other Secure-EL1 Payload (SP) then
864 `SMCCC`_ provides for such SMCs with the Trusted OS Call and Trusted
917 initialization. This happens prior to initializing a Trusted OS and running
946 OENs, e.g. SMCs to call a Trusted OS function. To optimize the lookup of a
1073 On a production system that includes a Trusted OS running in Secure-EL1/EL0,
1074 the Trusted OS is coupled with a companion runtime service in the BL31
1076 OS and all communications with it. The Trusted OS is the BL32 stage of the
1081 the *Secure-EL1 Payload* - as it is not always a Trusted OS.
[all …]
|