Searched refs:OS (Results 1 – 25 of 37) sorted by relevance
12
4 `OP-TEE OS`_ is a Trusted OS running as Secure EL1.9 There are two different modes for loading the OP-TEE OS. The default mode will11 platforms to use. There is also another technique that will load OP-TEE OS after15 understand the risks involved with allowing the Trusted OS to be loaded this30 .. _OP-TEE OS: https://github.com/OP-TEE/build
7 ProvenCore is a secure OS developed by ProvenRun S.A.S. using deductive formal methods.
20 TLK is a Trusted OS running as Secure EL1. It is a Free Open Source Software
1 PSCI OS-initiated mode31 OS-initiated.43 OS-initiated46 OS-initiated mode is optional.48 In OS-initiated mode, the calling OS is responsible for coordinating power55 There are two reasons why OS-initiated mode might be a more suitable option than65 In OS-initiated mode, the OS has knowledge of the next wakeup event for each75 In platform-coordinated mode, the OS doesn't have visibility when the last core76 at a power level enters a low-power state. If the OS wants to perform last man80 platform-coordinated mode when it should be using OS-initiated mode instead.[all …]
43 ifdef OS44 ifneq ($(findstring ${OS}, Windows_NT),)
35 for example an AArch32 Secure OS.57 - SPDs for the `OP-TEE Secure OS`_, `NVIDIA Trusted Little Kernel`_,58 `Trusty Secure OS`_ and `ProvenCore Secure OS`_.125 .. _OP-TEE Secure OS: https://github.com/OP-TEE/optee_os127 .. _Trusty Secure OS: https://source.android.com/security/trusty128 .. _ProvenCore Secure OS: https://provenrun.com/products/provencore/
73 entirely. Any bootloader or OS would need to setup the PMIC on its own then.137 Trusted OS dispatcher140 One can boot Trusted OS(OP-TEE OS, bl32 image) along side bl31 image on Allwinner A64.143 while compiling the bl31 image and make sure the loader (SPL) loads the Trusted OS binary to
74 Trusted OS dispatcher77 Tegra supports multiple Trusted OS'.84 This allows other Trusted OS vendors to use the upstream code and include87 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
24 OS, /* i: waiting for extra flags and operating system (gzip) */ enumerator
40 /* If required, SPD should enable loading of trusted OS fw config */
239 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and253 When invoked from the Hypervisor or OS kernel, the buffers are mapped into the258 caller, either it being the Hypervisor or OS kernel, as well as a secure267 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.285 (or OS Kernel if Hyp is absent), SPMD and SPMC.325 - An SP cannot send a direct request to an Hypervisor or OS kernel.326 - An Hypervisor or OS kernel can send a direct request to an SP or LSP.327 - An SP and LSP can send a direct response to an Hypervisor or OS kernel.343 The Hypervisor or OS kernel can issue the FFA_SPM_ID_GET call handled by the409 - The Hypervisor or OS kernel is the component initiating PSCI service calls.[all …]
115 (Hypervisor or OS kernel) to the SPMC.353 Secure Payload BL32 (Trusted OS): offset=0x1BCD1, size=0x15270, cmdline="--tos-fw"470 or the SPMC itself, the OS Kernel/Hypervisor, or other NWd VMs. The SPMC538 secure partitions. For this a VM (Hypervisor or OS kernel), or SP invokes one of:720 deployed in NWd, the Hypervisor or OS kernel must invoke the interface813 - Hypervisor or OS kernel in NS-EL1/EL2: the SPMD returns the SPMC version827 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and837 When invoked from the Hypervisor or OS kernel, the buffers are mapped into the846 caller, either it being the Hypervisor or OS kernel, as well as a secure855 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.[all …]
106 the higher level OS if the latter implements its own driver for the same
57 Note that if other privileged software, for example a Rich OS kernel, implements117 integrated, for example as part of a Trusted OS. Therefore any Variant 2133 applicable for TF. However, Secure Payloads (for example, Trusted OS) should
97 In case local workaround is not feasible, the Rich OS can invoke the SMC
22 Arm to support `PSCI`_, Secure Monitor for a Trusted OS and SoC specific42 reserved exclusively for Trusted OS providers or for interoperability with55 Fast 50-63 Trusted OS calls58 Yielding 2-63 Trusted OS Standard Calls305 Services that handle SMC Functions targeting a Trusted OS, Trusted Application,
77 Typically this is a TEE or Trusted OS, providing runtime secure services to the88 For example, UEFI or uboot. Its primary purpose is to boot a normal world OS.
76 include other runtime services, for example Trusted OS services. A guide
7 can be used if not updating the OpenSSL version on the OS. In order to do
98 by Trusted OS (OP-TEE OS, BL32). The TF-A only prepares CCU address translation windows100 When Trusted OS activates LLC SRAM, the CCU window target is changed to SRAM.101 There is no reason to enable this feature if OP-TEE OS built with CFG_WITH_PAGER=n.102 Only set LLC_SRAM=1 if OP-TEE OS is built with CFG_WITH_PAGER=y.
229 Trusted Little Kernel. A Trusted OS from NVIDIA.
96 | DF4 | | Secure world software (e.g. trusted OS) interact |100 | DF5 | | Non-secure world software (e.g. rich OS) interact |300 | | physically, through the Rich OS, or using the |947 | | untrusted binary as the secure OS.** |978 | | the non-secure OS must be considered a closed |
42 are loaded from that path instead of the default OS path. Export this
179 + EL1 BL32(Tee OS) | kernel195 + EL1 fip-ddr BL32(Tee OS) | kernel
311 - BL31 Trusted OS SPD code discovers that BL2 has not loaded the corresponding312 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
