| /Linux-v6.1/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
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 …]
|
| /Linux-v6.1/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-v6.1/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
|
| /Linux-v6.1/Documentation/powerpc/ |
| D | ultravisor.rst | 56 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-v6.1/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_ib.c | 139 bool secure; in amdgpu_ib_schedule() local
230 secure = false; in amdgpu_ib_schedule()
232 secure = ib->flags & AMDGPU_IB_FLAGS_SECURE; in amdgpu_ib_schedule()
233 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
240 if (secure != !!(ib->flags & AMDGPU_IB_FLAGS_SECURE)) { in amdgpu_ib_schedule()
241 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
242 secure = !secure; in amdgpu_ib_schedule()
243 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
252 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
|
| /Linux-v6.1/Documentation/devicetree/bindings/nvmem/ |
| D | amlogic-efuse.txt | 7 - secure-monitor: phandle to the secure-monitor node
20 secure-monitor = <&sm>;
35 sm: secure-monitor {
|
| /Linux-v6.1/arch/arm64/boot/dts/tesla/ |
| D | fsd.dtsi | 364 interrupts = <GIC_SPI 438 IRQ_TYPE_LEVEL_HIGH>, /* Global secure fault */
365 <GIC_SPI 439 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */
366 <GIC_SPI 451 IRQ_TYPE_LEVEL_HIGH>, /* Combined secure interrupt */
367 <GIC_SPI 450 IRQ_TYPE_LEVEL_HIGH>, /* Combined non-secure interrupt */
372 /* Per context non-secure context interrupts, 0-3 interrupts */
384 interrupts = <GIC_SPI 321 IRQ_TYPE_LEVEL_HIGH>, /* Global secure fault */
385 <GIC_SPI 322 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */
386 <GIC_SPI 346 IRQ_TYPE_LEVEL_HIGH>, /* Combined secure interrupt */
387 <GIC_SPI 345 IRQ_TYPE_LEVEL_HIGH>, /* Combined non-secure interrupt */
396 /* Per context non-secure context interrupts, 0-7 interrupts */
[all …]
|
| /Linux-v6.1/fs/ |
| D | anon_inodes.c | 82 bool secure) in __anon_inode_getfile() argument
90 if (secure) { in __anon_inode_getfile()
184 bool secure) in __anon_inode_getfd() argument
195 secure); in __anon_inode_getfd()
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-secvar | 5 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
|
| /Linux-v6.1/arch/s390/crypto/ |
| D | Kconfig | 22 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
33 SHA-1 secure hash algorithm (FIPS 180)
44 SHA-224 and SHA-256 secure hash algorithms (FIPS 180)
55 SHA3-224 and SHA3-256 secure hash algorithms (FIPS 202)
66 SHA3-384 and SHA3-512 secure hash algorithms (FIPS 202)
|
| /Linux-v6.1/arch/arm/mach-omap2/ |
| D | Makefile | 16 secure-common = omap-smc.o omap-secure.o
19 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
20 obj-$(CONFIG_ARCH_OMAP4) += $(secure-common)
21 obj-$(CONFIG_SOC_AM33XX) += $(secure-common)
22 obj-$(CONFIG_SOC_OMAP5) += $(secure-common)
23 obj-$(CONFIG_SOC_AM43XX) += $(secure-common)
24 obj-$(CONFIG_SOC_DRA7XX) += $(secure-common)
|
| /Linux-v6.1/Documentation/staging/ |
| D | tee.rst | 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
139 separate secure co-processor.
172 RPC (Remote Procedure Call) are requests from secure world to kernel driver
190 There are two kinds of notifications that secure world can use to make
195 2. Asynchronous notifications delivered with a combination of a non-secure
196 edge-triggered interrupt and a fast call from the non-secure interrupt
200 this is only usable when secure world is entered with a yielding call via
201 ``OPTEE_SMC_CALL_WITH_ARG``. This excludes such notifications from secure
204 An asynchronous notification is delivered via a non-secure edge-triggered
[all …]
|
| /Linux-v6.1/arch/powerpc/crypto/ |
| D | Kconfig | 51 SHA-1 secure hash algorithm (FIPS 180)
59 SHA-1 secure hash algorithm (FIPS 180)
70 SHA-224 and SHA-256 secure hash algorithms (FIPS 180)
93 timining attacks. Nevertheless it might be not as secure as other
|
| /Linux-v6.1/arch/arm64/boot/dts/arm/ |
| D | corstone1000.dtsi | 148 secure-status = "okay"; /* secure-world-only */
160 secure-status = "okay"; /* secure-world-only */
|
| /Linux-v6.1/Documentation/driver-api/firmware/ |
| D | other_interfaces.rst | 25 higher than the kernel is granted. Such secure features include
31 drivers to request access to the secure features. The requests are queued
33 of the requests on to a secure monitor (EL3).
|
| /Linux-v6.1/arch/mips/crypto/ |
| D | Kconfig | 39 SHA-1 secure hash algorithm (FIPS 180)
49 SHA-224 and SHA-256 secure hash algorithms (FIPS 180)
59 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
|
| /Linux-v6.1/Documentation/devicetree/bindings/firmware/meson/ |
| D | meson_sm.txt | 6 Required properties for the secure monitor node:
12 sm: secure-monitor {
|
| /Linux-v6.1/Documentation/devicetree/bindings/misc/ |
| D | brcm,kona-smc.txt | 4 used for non-secure to secure communications.
|
| /Linux-v6.1/drivers/vfio/ |
| D | Kconfig | 8 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-v6.1/arch/arm64/crypto/ |
| D | Kconfig | 45 SHA-1 secure hash algorithm (FIPS 180)
54 SHA-224 and SHA-256 secure hash algorithms (FIPS 180)
64 SHA-224 and SHA-256 secure hash algorithms (FIPS 180)
73 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
83 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
94 SHA-3 secure hash algorithms (FIPS 202)
105 SM3 (ShangMi 3) secure hash function (OSCCA GM/T 0004-2012)
|
| /Linux-v6.1/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-v6.1/Documentation/devicetree/bindings/firmware/ |
| D | intel,stratix10-svc.txt | 10 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-v6.1/Documentation/security/ |
| D | siphash.rst | 7 SipHash is a cryptographically secure PRF -- a keyed hash function -- that
15 indistinguishable from random. You may then use that integer as part of secure
16 sequence numbers, secure cookies, or mask it off for use in a hash table.
21 Keys should always be generated from a cryptographically secure source of
137 same as the siphash ones, or that they are secure; the hsiphash functions still
138 use a less secure reduced-round algorithm and truncate their outputs to 32
144 Keys should always be generated from a cryptographically secure source of
|
| /Linux-v6.1/arch/sparc/crypto/ |
| D | Kconfig | 45 SHA-1 secure hash algorithm (FIPS 180)
55 SHA-224 and SHA-256 secure hash algorithms (FIPS 180)
65 SHA-384 and SHA-512 secure hash algorithms (FIPS 180)
|
