| /linux/drivers/firmware/qcom/ |
| H A D | Kconfig | 18 prompt "TrustZone interface memory allocator mode"
23 suitable format for sharing with the TrustZone. If in doubt, select
39 With this selected, all buffers passed to the TrustZone must be allocated
40 using the TZMem allocator or else the TrustZone will refuse to use them.
|
| H A D | qcom_tzmem.c | 3 * Memory allocator for buffers shared with the TrustZone.
194 * Create a new pool of memory suitable for sharing with the TrustZone.
479 MODULE_DESCRIPTION("TrustZone memory allocator for Qualcomm firmware drivers");
|
| /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.
|
| /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()
|
| /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 earlier CPUs such as TrustZone and multicore (MPCore).
28 (HBI-0147) was created as a development board to test ARM TrustZone,
|
| /linux/Documentation/devicetree/bindings/bus/ |
| H A D | st,stm32-etzpc.yaml | 7 title: STM32 Extended TrustZone protection controller
10 The ETZPC configures TrustZone security in a SoC having bus masters and
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-vf610.yaml | 41 - description: GPIO Trustzone non-secure interrupt number
42 - description: GPIO Trustzone secure interrupt number
|
| /linux/arch/arm/boot/dts/mediatek/ |
| H A D | mt8127.dtsi | 50 trustzone-bootinfo@80002000 {
51 compatible = "mediatek,trustzone-bootinfo";
|
| H A D | mt8135.dtsi | 75 trustzone-bootinfo@80002000 {
76 compatible = "mediatek,trustzone-bootinfo";
|
| /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-db8500.dtsi | 42 * to actually call into trustzone to run secure
|
| H A D | ste-db8520.dtsi | 42 * to actually call into trustzone to run secure
|
| /linux/Documentation/tee/ |
| H A D | tee.rst | 13 TrustZone on ARM CPUs, or a separate secure co-processor etc. A TEE driver
|
| H A D | op-tee.rst | 8 TrustZone based OP-TEE solution that is supported.
22 to tell, for instance, a TrustZone OP-TEE apart from an OP-TEE running on a
|
| /linux/arch/arm/common/ |
| H A D | secure_cntvoff.S | 16 * mode or secure Monitor mode with SCR.NS==1. If TrustZone is enabled
|
| /linux/Documentation/devicetree/bindings/crypto/ |
| H A D | arm,cryptocell.yaml | 7 title: Arm TrustZone CryptoCell cryptographic engine
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A D | qcom,venus-common.yaml | 56 have TrustZone.
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm_ftpm_tee.rst | 11 This driver is a shim for firmware implemented in ARM's TrustZone
|
| /linux/Documentation/devicetree/bindings/soc/mediatek/ |
| H A D | devapc.yaml | 11 MediaTek bus fabric provides TrustZone security support and data
|
| /linux/Documentation/devicetree/bindings/tpm/ |
| H A D | microsoft,ftpm.yaml | 20 Microsoft's firmware-based TPM 2.0 (fTPM) leverages ARM TrustZone to overcome
|
| /linux/Documentation/devicetree/bindings/arm/firmware/ |
| H A D | linaro,optee-tz.yaml | 14 Execution Environment. The security can be provided with ARM TrustZone, but
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | nand-chip.yaml | 66 like Trustzone. This property contains the start address and size of
|
| /linux/Documentation/arch/arm/ |
| H A D | firmware.rst | 7 Some boards are running with secure firmware running in TrustZone secure
|
| /linux/drivers/soc/qcom/ |
| H A D | ice.c | 133 * usable by Linux, the TrustZone software also needs to support certain in qcom_ice_check_supported()
251 * slave. Without this, TrustZone cannot program keys into ICE. in qcom_ice_hwkm_init()
327 /* Call into TrustZone to program the wrapped key using HWKM. */ in qcom_ice_program_wrapped_key()
|