| /Linux-v4.19/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
18 "vendor,secure-foo". If there is no "secure-" property then the Secure
21 validly have "secure-" versions; this list will be enlarged on a
26 still be processed unmodified by existing Non-secure software (and in
32 secure- bindings only need to be used where both the Secure and Normal
37 - secure-status : specifies whether the device is present and usable
38 in the secure world. The combination of this with "status" allows
40 specified. If "secure-status" is not specified it defaults to the
46 secure-status = "okay"; /* visible in both */
[all …]
|
| D | juno,scpi.txt | 8 - compatible : should be "arm,juno-sram-ns" for Non-secure SRAM
14 - compatible : should be "arm,juno-scp-shmem" for Non-secure SRAM based
|
| D | pmu.txt | 55 - secure-reg-access : Indicates that the ARMv7 Secure Debug Enable Register
57 any setup required that is only possible in ARMv7 secure
63 in Non-secure state.
|
| D | amlogic.txt | 108 secure firmware.
111 - compatible: For Meson GX SoCs, must be "amlogic,meson-gx-ao-secure", "syscon"
127 ao-secure@140 {
128 compatible = "amlogic,meson-gx-ao-secure", "syscon";
|
| /Linux-v4.19/Documentation/devicetree/bindings/crypto/ |
| D | inside-secure-safexcel.txt | 4 - compatible: Should be "inside-secure,safexcel-eip197b",
5 "inside-secure,safexcel-eip197d" or
6 "inside-secure,safexcel-eip97ies".
21 - "inside-secure,safexcel-eip197" is equivalent to
22 "inside-secure,safexcel-eip197b".
23 - "inside-secure,safexcel-eip97" is equivalent to
24 "inside-secure,safexcel-eip97ies".
29 compatible = "inside-secure,safexcel-eip197b";
|
| /Linux-v4.19/Documentation/devicetree/bindings/iommu/ |
| D | qcom,iommu.txt | 6 to non-secure vs secure interrupt line.
31 - qcom,iommu-secure-id : secure-id.
37 - "qcom,msm-iommu-v1-ns" : non-secure context bank
38 - "qcom,msm-iommu-v1-sec" : secure context bank
46 for routing of context bank irq's to secure vs non-
47 secure lines. (Ie. if the iommu contains secure
63 qcom,iommu-secure-id = <17>;
89 qcom,iommu-secure-id = <18>;
|
| D | msm,iommu-v0.txt | 12 support secure mode two interrupts must be specified, for non-secure and
13 secure mode, in that order. For instances that don't support secure mode a
|
| D | renesas,ipmmu-vmsa.txt | 32 support secure mode two interrupts must be specified, for non-secure and
33 secure mode, in that order. For instances that don't support secure mode a
|
| D | arm,smmu.txt | 57 - calxeda,smmu-secure-config-access : Enable proper handling of buggy
58 implementations that always use secure access to
59 SMMU configuration registers. In this case non-secure
60 aliases of secure registers have to be used during
|
| /Linux-v4.19/arch/arm/firmware/ |
| D | Kconfig | 12 bool "Trusted Foundations secure monitor support"
17 market) are booted with the Trusted Foundations secure monitor
18 active, requiring some core operations to be performed by the secure
21 This option allows the kernel to invoke the secure monitor whenever
|
| /Linux-v4.19/Documentation/devicetree/bindings/rng/ |
| D | omap_rng.txt | 9 - "inside-secure,safexcel-eip76" for SoCs with EIP76 IP block
14 Used for "ti,omap4-rng" and "inside-secure,safexcel-eip76"
16 "inside-secure,safexcel-eip76" compatible, the second clock is
34 compatible = "inside-secure,safexcel-eip76";
|
| /Linux-v4.19/arch/arm/crypto/ |
| D | Kconfig | 17 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
27 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
37 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
46 SHA-256 secure hash standard (DFIPS 180-2) implemented
54 SHA-256 secure hash standard (DFIPS 180-2) implemented
62 SHA-512 secure hash standard (DFIPS 180-2) implemented
79 Use a faster and more secure NEON based implementation of AES in CBC,
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/sunxi/ |
| D | smp-sram.txt | 4 Allwinner's A80 SoC uses part of the secure sram for hotplugging of the
13 ../../sram/sunxi-sram.txt. This SRAM is secure only and not mappable to
16 Also there are no "secure-only" properties. The implementation should
29 /* 256 KiB secure SRAM at 0x20000 */
|
| /Linux-v4.19/Documentation/devicetree/bindings/sram/ |
| D | samsung-sram.txt | 9 declaration. These nodes are of two types depending upon secure or
10 non-secure execution environment.
15 "samsung,exynos4210-sysram-ns" : for Non-secure SYSRAM
|
| /Linux-v4.19/Documentation/devicetree/bindings/firmware/meson/ |
| D | meson_sm.txt | 6 Required properties for the secure monitor node:
12 sm: secure-monitor {
|
| /Linux-v4.19/Documentation/devicetree/bindings/mailbox/ |
| D | ti,secure-proxy.txt | 4 The Texas Instruments' secure proxy is a mailbox controller that has
15 - compatible: Shall be "ti,am654-secure-proxy"
32 compatible = "ti,am654-secure-proxy";
|
| /Linux-v4.19/Documentation/devicetree/bindings/misc/ |
| D | brcm,kona-smc.txt | 4 used for non-secure to secure communications.
|
| /Linux-v4.19/drivers/vfio/ |
| D | Kconfig | 27 VFIO provides a framework for secure userspace device drivers.
38 considered secure. VFIO No-IOMMU mode enables IOMMU groups for
40 infrastructure in a non-secure mode. Use of this mode will result
|
| /Linux-v4.19/Documentation/devicetree/bindings/timer/ |
| D | ti,timer.txt | 32 - ti,timer-secure: Indicates the timer is reserved on a secure OMAP device
43 ti,timer-secure;
|
| /Linux-v4.19/arch/arm/mach-omap2/ |
| D | Makefile | 17 secure-common = omap-smc.o omap-secure.o
20 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
21 obj-$(CONFIG_ARCH_OMAP4) += $(hwmod-common) $(secure-common)
23 obj-$(CONFIG_SOC_OMAP5) += $(hwmod-common) $(secure-common)
24 obj-$(CONFIG_SOC_AM43XX) += $(hwmod-common) $(secure-common)
25 obj-$(CONFIG_SOC_DRA7XX) += $(hwmod-common) $(secure-common)
|
| /Linux-v4.19/drivers/of/ |
| D | kobj.c | 68 bool secure = strncmp(pp->name, "security-", 9) == 0; in __of_add_property_sysfs() local
78 pp->attr.attr.mode = secure ? 0400 : 0444; in __of_add_property_sysfs()
79 pp->attr.size = secure ? 0 : pp->length; in __of_add_property_sysfs()
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-boards.txt | 76 - firmware node, specifying presence and type of secure firmware:
77 - compatible: only "samsung,secure-firmware" is currently supported
78 - reg: address of non-secure SYSRAM used for communication with firmware
81 compatible = "samsung,secure-firmware";
|
| /Linux-v4.19/drivers/gpu/drm/nouveau/nvkm/falcon/ |
| D | base.c | 28 u32 size, u16 tag, u8 port, bool secure) in nvkm_falcon_load_imem() argument
30 if (secure && !falcon->secret) { in nvkm_falcon_load_imem()
37 secure); in nvkm_falcon_load_imem()
|
| /Linux-v4.19/drivers/memory/tegra/ |
| D | mc.c | 463 const char *direction, *secure; in tegra_mc_irq() local
486 secure = "secure "; in tegra_mc_irq()
488 secure = ""; in tegra_mc_irq()
536 client, secure, direction, &addr, error, in tegra_mc_irq()
558 const char *direction = "read", *secure = ""; in tegra20_mc_irq() local
588 secure = "secure "; in tegra20_mc_irq()
602 client, secure, direction, &addr, error, in tegra20_mc_irq()
|
| /Linux-v4.19/Documentation/ |
| D | tee.txt | 8 secure environment, for example, TrustZone on ARM CPUs, or a separate
9 secure co-processor etc. A TEE driver handles the details needed to
75 separate secure co-processor.
108 RPC (Remote Procedure Call) are requests from secure world to kernel driver
|
