| /openbmc/u-boot/doc/ |
| H A D | README.fsl-trustzone-components | 1 Freescale ARM64 SoCs like LS2080A have ARM TrustZone components like
2 TZPC-BP147 (TrustZone Protection Controller) and TZASC-400 (TrustZone
12 TZPC-BP147 (TrustZone Protection Controller)
19 TZASC-400 (TrustZone Address Space Controller)
|
| H A D | README.tee | 8 secure environment, for example, TrustZone on ARM CPUs, or a separate
48 TrustZone based OP-TEE solution that is supported.
62 to tell, for instance, a TrustZone OP-TEE apart from an OP-TEE running on a
|
| /openbmc/linux/Documentation/devicetree/bindings/rng/ |
| H A D | arm-cctrng.yaml | 7 title: Arm TrustZone CryptoCell TRNG engine
13 Arm TrustZone CryptoCell TRNG (True Random Number Generator) engine.
29 Arm TrustZone CryptoCell TRNG engine has 4 ring oscillators.
|
| /openbmc/linux/arch/arm/mach-mediatek/ |
| H A D | platsmp.c | 77 static void __init __mtk_smp_prepare_cpus(unsigned int max_cpus, int trustzone) in __mtk_smp_prepare_cpus() argument
82 if (trustzone) { in __mtk_smp_prepare_cpus()
103 if (trustzone) { in __mtk_smp_prepare_cpus()
104 /* smp_base(trustzone-bootinfo) is reserved by device tree */ in __mtk_smp_prepare_cpus()
|
| /openbmc/linux/drivers/remoteproc/ |
| H A D | Kconfig | 191 for the non-TrustZone part of Qualcomm Technology Inc. ADSP and CDSP
192 remote processors. The TrustZone part is handled by QCOM_Q6V5_PAS
212 subsystem based on Hexagon V5. The TrustZone based system is
231 Say y here to support the TrustZone based Peripheral Image Loader
255 a non-TrustZone wireless subsystem.
288 System (PAS) in TrustZone.
|
| /openbmc/u-boot/doc/device-tree-bindings/firmware/ |
| H A D | linaro,optee-tz.txt | 4 Execution Environment. The security can be provided with ARM TrustZone, but
10 * OP-TEE based on ARM TrustZone required properties:
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | vexpress.rst | 43 - BP147 TrustZone Protection Controller
44 - TrustZone Address Space Controller
53 TrustZone or the Virtualization Extensions: if you want these you
|
| H A D | virt.rst | 43 - Secure-World-only devices if the CPU has TrustZone:
53 TrustZone emulation is not enabled.
103 Arm Security Extensions (TrustZone). The default is ``off``.
|
| H A D | xlnx-zcu102.rst | 14 Arm Security Extensions (TrustZone). The default is ``off``.
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ |
| H A D | secure.txt | 3 ARM CPUs with TrustZone support have two distinct address spaces,
5 kernel) are not TrustZone aware and run entirely in either the Normal
7 TrustZone aware and need to be able to determine whether devices are
|
| H A D | arm,realview.yaml | 15 the earlier CPUs such as TrustZone and multicore (MPCore).
28 (HBI-0147) was created as a development board to test ARM TrustZone,
|
| /openbmc/qemu/include/hw/misc/ |
| H A D | tz-mpc.h | 2 * ARM AHB5 TrustZone Memory Protection Controller emulation
12 /* This is a model of the TrustZone memory protection controller (MPC).
|
| H A D | tz-msc.h | 2 * ARM TrustZone master security controller emulation
13 * This is a model of the TrustZone master security controller (MSC).
|
| H A D | tz-ppc.h | 2 * ARM TrustZone peripheral protection controller emulation
12 /* This is a model of the TrustZone peripheral protection controller (PPC).
|
| /openbmc/u-boot/board/freescale/ls1021atwr/ |
| H A D | README | 66 - QorIQ Trust Architecture, Secure Boot, and ARM TrustZone supported
75 - QorIQ TrustArchitecture with Secure Boot, as well as ARM TrustZone supported
|
| /openbmc/linux/arch/arm/boot/dts/mediatek/ |
| H A D | mt8127.dtsi | 50 trustzone-bootinfo@80002000 {
51 compatible = "mediatek,trustzone-bootinfo";
|
| /openbmc/u-boot/board/freescale/ls1021aqds/ |
| H A D | README | 66 - QorIQ Trust Architecture, Secure Boot, and ARM TrustZone supported
75 - QorIQ TrustArchitecture with Secure Boot, as well as ARM TrustZone supported
|
| /openbmc/linux/Documentation/staging/ |
| H A D | tee.rst | 8 secure environment, for example, TrustZone on ARM CPUs, or a separate
124 TrustZone based OP-TEE solution that is supported.
138 to tell, for instance, a TrustZone OP-TEE apart from an OP-TEE running on a
275 is a dedicated processor that features ARM TrustZone technology, along with a
|
| /openbmc/u-boot/drivers/tee/optee/ |
| H A D | Kconfig | 8 ARM TrustZone(R) technology as the underlying hardware isolation
|
| /openbmc/linux/arch/arm/boot/dts/st/ |
| H A D | ste-db9500.dtsi | 24 * to actually call into trustzone to run secure
|
| H A D | ste-db8520.dtsi | 42 * to actually call into trustzone to run secure
|
| /openbmc/u-boot/arch/arm/mach-tegra/ |
| H A D | ap.c | 198 * is restricted to TrustZone-secured requestors. The kernel will use in smmu_enable()
208 * to TrustZone-secured requestors. in smmu_enable()
|
| /openbmc/u-boot/drivers/tee/ |
| H A D | Kconfig | 9 environment, for example, TrustZone on ARM cpus, or a separate
|
| /openbmc/linux/arch/arm/common/ |
| H A D | secure_cntvoff.S | 16 * mode or secure Monitor mode with SCR.NS==1. If TrustZone is enabled
|
| /openbmc/linux/Documentation/devicetree/bindings/crypto/ |
| H A D | arm,cryptocell.yaml | 7 title: Arm TrustZone CryptoCell cryptographic engine
|