Home
last modified time | relevance | path

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

12345678910

/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/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";
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/amdgpu/
Damdgpu_ib.c137 bool secure; in amdgpu_ib_schedule() local
232 secure = false; in amdgpu_ib_schedule()
234 secure = ib->flags & AMDGPU_IB_FLAGS_SECURE; in amdgpu_ib_schedule()
235 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
242 if (secure != !!(ib->flags & AMDGPU_IB_FLAGS_SECURE)) { in amdgpu_ib_schedule()
243 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
244 secure = !secure; in amdgpu_ib_schedule()
245 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
254 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/nvmem/
Damlogic-efuse.txt7 - secure-monitor: phandle to the secure-monitor node
20 secure-monitor = <&sm>;
35 sm: secure-monitor {
/kernel/linux/linux-5.10/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";
Domap3_rom_rng.txt3 Secure SoCs may provide RNG via secure ROM calls like Nokia N900 does. The
4 implementation can depend on the SoC secure ROM used.
/kernel/linux/linux-5.10/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
90 Use a faster and more secure NEON based implementation of AES in CBC,
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-secvar5 secureboot, thereby secure variables. It exposes interface
6 for reading/writing the secure variables
11 Description: This directory lists all the secure variables that are supported
24 Description: Each secure variable is represented as a directory named as
/kernel/linux/linux-5.10/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)
22 obj-$(CONFIG_SOC_AM33XX) += $(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)
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/firmware/meson/
Dmeson_sm.txt6 Required properties for the secure monitor node:
12 sm: secure-monitor {
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/rockchip/
Dgrf.txt7 - GRF, used for general non-secure system,
8 - SGRF, used for general secure system,
14 - GRF, used for general non-secure system,
15 - SGRF, used for general secure system,
/kernel/linux/linux-5.10/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).
/kernel/linux/linux-5.10/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";
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/misc/
Dbrcm,kona-smc.txt4 used for non-secure to secure communications.
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/
Dti,timer.txt32 - ti,timer-secure: Indicates the timer is reserved on a secure OMAP device
43 ti,timer-secure;
/kernel/linux/linux-5.10/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()
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/drivers/memory/tegra/
Dmc.c438 const char *direction, *secure; in tegra_mc_irq() local
461 secure = "secure "; in tegra_mc_irq()
463 secure = ""; in tegra_mc_irq()
511 client, secure, direction, &addr, error, in tegra_mc_irq()
533 const char *direction = "read", *secure = ""; in tegra20_mc_irq() local
570 secure = "secure "; in tegra20_mc_irq()
584 client, secure, direction, &addr, error, in tegra20_mc_irq()
/kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/nvkm/falcon/
Dbase.c29 u32 size, u16 tag, u8 port, bool secure) in nvkm_falcon_load_imem() argument
31 if (secure && !falcon->secret) { in nvkm_falcon_load_imem()
38 secure); in nvkm_falcon_load_imem()
/kernel/linux/linux-5.10/drivers/firmware/
DKconfig214 and manages secure monitor call to communicate with secure monitor
215 software at secure monitor exception level.
270 bool "Trusted Foundations secure monitor support"
274 the market) are booted with the Trusted Foundations secure monitor
275 active, requiring some core operations to be performed by the secure
278 This option allows the kernel to invoke the secure monitor whenever
286 tristate "Turris Mox rWTM secure firmware driver"
293 This driver communicates with the firmware on the Cortex-M3 secure

12345678910