Home
last modified time | relevance | path

Searched full:trustzone (Results 1 – 25 of 31) sorted by relevance

12

/linux/drivers/firmware/qcom/
H A Dqcom_pas.c119 * not embedded in the firmware binary and instead are provided by TrustZone.
120 * However, dynamic resources are always expected to come from TrustZone. This
122 * be provided by TrustZone PAS service.
125 * should be passed in input_rt. These will be forwarded to TrustZone for
126 * authentication. TrustZone will then append the dynamic resources and return
139 * @output_rt_size: TrustZone expects caller should pass worst case size for
145 * TrustZone. The caller is responsible for freeing the buffer. On failure,
191 * TrustZone accesses the firmware memory region for authentication. The
H A DKconfig39 bool "TrustZone interface memory allocator: SHM Bridge"
46 With this selected, all buffers passed to the TrustZone must be allocated
47 using the TZMem allocator or else the TrustZone will refuse to use them.
H A Dqcom_tzmem.c3 * Memory allocator for buffers shared with the TrustZone.
238 * Create a new pool of memory suitable for sharing with the TrustZone.
525 MODULE_DESCRIPTION("TrustZone memory allocator for Qualcomm firmware drivers");
H A Dqcom_scm.c752 * resource table TrustZone sends, response code in res.result[1] as in __qcom_scm_pas_mem_setup()
795 * TrustZone can not accept buffer as NULL value as argument hence, in __qcom_scm_pas_get_rsc_table()
830 /* A zero-sized table means that TrustZone has no resource table. */ in __qcom_scm_pas_get_rsc_table2()
896 * memory region and then invokes a call to TrustZone to authenticate. in qcom_scm_pas_get_rsc_table()
903 * subsequently call TrustZone for authenticate and reset. in __qcom_scm_pas_auth_and_reset()
2089 * the TrustZone. in __qcom_scm_qseecom_call()
2786 "Failed to enable the TrustZone memory allocator\n");
2827 * be called after the TrustZone memory pool is initialized and the in qcom_scm_probe()
/linux/Documentation/devicetree/bindings/rng/
H A Darm-cctrng.yaml7 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 Dplatsmp.c85 static void __init __mtk_smp_prepare_cpus(unsigned int max_cpus, int trustzone) in __mtk_smp_prepare_cpus() argument
90 if (trustzone) { in __mtk_smp_prepare_cpus()
111 if (trustzone) { in __mtk_smp_prepare_cpus()
112 /* smp_base(trustzone-bootinfo) is reserved by device tree */ in __mtk_smp_prepare_cpus()
/linux/Documentation/devicetree/bindings/arm/
H A Dsecure.txt3 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 Darm,realview.yaml15 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/gpio/
H A Dgpio-vf610.yaml41 - description: GPIO Trustzone non-secure interrupt number
42 - description: GPIO Trustzone secure interrupt number
/linux/arch/arm/boot/dts/st/
H A Dste-db9500.dtsi24 * to actually call into trustzone to run secure
H A Dste-db8500.dtsi42 * to actually call into trustzone to run secure
H A Dste-db8520.dtsi42 * to actually call into trustzone to run secure
/linux/Documentation/tee/
H A Dtee.rst13 TrustZone on ARM CPUs, or a separate secure co-processor etc. A TEE driver
H A Dop-tee.rst8 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
H A Damd-tee.rst11 is a dedicated processor that features ARM TrustZone technology, along with a
/linux/arch/arm/common/
H A Dsecure_cntvoff.S16 * mode or secure Monitor mode with SCR.NS==1. If TrustZone is enabled
/linux/Documentation/devicetree/bindings/crypto/
H A Darm,cryptocell.yaml7 title: Arm TrustZone CryptoCell cryptographic engine
/linux/Documentation/security/tpm/
H A Dtpm_ftpm_tee.rst11 This driver is a shim for firmware implemented in ARM's TrustZone
/linux/Documentation/devicetree/bindings/soc/mediatek/
H A Ddevapc.yaml11 MediaTek bus fabric provides TrustZone security support and data
/linux/Documentation/devicetree/bindings/tpm/
H A Dmicrosoft,ftpm.yaml20 Microsoft's firmware-based TPM 2.0 (fTPM) leverages ARM TrustZone to overcome
/linux/Documentation/arch/arm/
H A Dfirmware.rst7 Some boards are running with secure firmware running in TrustZone secure
H A Dtcm.rst48 world (TrustZone).
/linux/arch/arm/kernel/
H A Dtcm.c316 * were inaccessible due to TrustZone configuration. in tcm_init()
354 * were inaccessible due to TrustZone configuration. in tcm_init()
/linux/arch/arm/mach-imx/
H A Dtzic.c192 pr_info("TrustZone Interrupt Controller (TZIC) initialized\n"); in tzic_init_dt()
/linux/arch/arm/boot/dts/mediatek/
H A Dmt2701.dtsi55 trustzone-bootinfo@80002000 {
56 compatible = "mediatek,trustzone-bootinfo";

12