Home
last modified time | relevance | path

Searched refs:secure (Results 1 – 25 of 199) sorted by relevance

12345678

/Linux-v5.4/Documentation/devicetree/bindings/arm/
Dsecure.txt15 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
38 - secure-status : specifies whether the device is present and usable
39 in the secure world. The combination of this with "status" allows
41 specified. If "secure-status" is not specified it defaults to the
47 secure-status = "okay"; /* visible in both */
[all …]
Djuno,scpi.txt8 - compatible : should be "arm,juno-sram-ns" for Non-secure SRAM
14 - compatible : should be "arm,juno-scp-shmem" for Non-secure SRAM based
/Linux-v5.4/Documentation/devicetree/bindings/crypto/
Dinside-secure-safexcel.txt4 - 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-v5.4/Documentation/devicetree/bindings/iommu/
Dqcom,iommu.txt6 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>;
Dmsm,iommu-v0.txt12 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
Drenesas,ipmmu-vmsa.txt35 support secure mode two interrupts must be specified, for non-secure and
36 secure mode, in that order. For instances that don't support secure mode a
/Linux-v5.4/Documentation/powerpc/
Dultravisor.rst56 process is running in secure mode, MSR(S) bit 41. MSR(S)=1, process
57 is in secure mode, MSR(s)=0 process is in normal mode.
63 the VM it is returning to is secure.
101 * Memory is partitioned into secure and normal memory. Only processes
102 that are running in secure mode can access secure memory.
104 * The hardware does not allow anything that is not running secure to
105 access secure memory. This means that the Hypervisor cannot access
110 * I/O systems are not allowed to directly address secure memory. This
117 * When a process is running in secure mode all hypercalls
120 * When a process is in secure mode all interrupts go to the
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/rng/
Domap_rng.txt9 - "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-v5.4/Documentation/devicetree/bindings/arm/sunxi/
Dsmp-sram.txt4 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-v5.4/arch/arm/crypto/
DKconfig17 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
88 Use a faster and more secure NEON based implementation of AES in CBC,
/Linux-v5.4/Documentation/devicetree/bindings/sram/
Dsamsung-sram.txt9 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-v5.4/Documentation/devicetree/bindings/firmware/meson/
Dmeson_sm.txt6 Required properties for the secure monitor node:
12 sm: secure-monitor {
/Linux-v5.4/Documentation/devicetree/bindings/mailbox/
Dti,secure-proxy.txt4 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-v5.4/Documentation/driver-api/firmware/
Dother_interfaces.rst19 higher than the kernel is granted. Such secure features include
25 drivers to request access to the secure features. The requests are queued
27 of the requests on to a secure monitor (EL3).
/Linux-v5.4/Documentation/devicetree/bindings/misc/
Dbrcm,kona-smc.txt4 used for non-secure to secure communications.
/Linux-v5.4/drivers/vfio/
DKconfig27 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-v5.4/arch/arm/mach-omap2/
DMakefile17 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-v5.4/Documentation/devicetree/bindings/timer/
Dti,timer.txt32 - ti,timer-secure: Indicates the timer is reserved on a secure OMAP device
43 ti,timer-secure;
/Linux-v5.4/drivers/of/
Dkobj.c68 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-v5.4/Documentation/devicetree/bindings/firmware/
Dintel,stratix10-svc.txt10 communication with SDM, only the secure world of software (EL3, Exception
18 driver also manages secure monitor call (SMC) to communicate with secure monitor
/Linux-v5.4/Documentation/devicetree/bindings/arm/samsung/
Dsamsung-boards.txt76 - 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-v5.4/drivers/gpu/drm/nouveau/nvkm/falcon/
Dbase.c28 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-v5.4/drivers/memory/tegra/
Dmc.c468 const char *direction, *secure; in tegra_mc_irq() local
491 secure = "secure "; in tegra_mc_irq()
493 secure = ""; in tegra_mc_irq()
541 client, secure, direction, &addr, error, in tegra_mc_irq()
563 const char *direction = "read", *secure = ""; in tegra20_mc_irq() local
600 secure = "secure "; in tegra20_mc_irq()
614 client, secure, direction, &addr, error, in tegra20_mc_irq()
/Linux-v5.4/Documentation/
Dtee.txt8 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
/Linux-v5.4/arch/x86/kernel/cpu/
Dbugs.c527 bool secure; member
538 static void __init spec_v2_user_print_cond(const char *reason, bool secure) in spec_v2_user_print_cond() argument
540 if (boot_cpu_has_bug(X86_BUG_SPECTRE_V2) != secure) in spec_v2_user_print_cond()
567 v2_user_options[i].secure); in spectre_v2_parse_user_cmdline()
671 bool secure; member
681 static void __init spec_v2_print_cond(const char *reason, bool secure) in spec_v2_print_cond() argument
683 if (boot_cpu_has_bug(X86_BUG_SPECTRE_V2) != secure) in spec_v2_print_cond()
729 mitigation_options[i].secure); in spectre_v2_parse_cmdline()

12345678