Home
last modified time | relevance | path

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

12345678910>>...14

/linux-6.3-rc2/Documentation/devicetree/bindings/arm/
A 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
39 in the secure world. The combination of this with "status" allows
41 specified. If "secure-status" is not specified it defaults to the
50 secure-status = "disabled"; /* NS-only */
51 status = "okay"; secure-status = "disabled"; /* NS-only */
52 status = "disabled"; secure-status = "okay"; /* S-only */
56 The secure-chosen node
[all …]
/linux-6.3-rc2/Documentation/devicetree/bindings/crypto/
A 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-6.3-rc2/Documentation/devicetree/bindings/iommu/
A Dqcom,iommu.txt6 to non-secure vs secure interrupt line.
32 - qcom,iommu-secure-id : secure-id.
38 - "qcom,msm-iommu-v1-ns" : non-secure context bank
39 - "qcom,msm-iommu-v1-sec" : secure context bank
47 for routing of context bank irq's to secure vs non-
48 secure lines. (Ie. if the iommu contains secure
64 qcom,iommu-secure-id = <17>;
90 qcom,iommu-secure-id = <18>;
A 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
/linux-6.3-rc2/Documentation/devicetree/bindings/arm/amlogic/
A Damlogic,meson-gx-ao-secure.yaml5 $id: "http://devicetree.org/schemas/arm/amlogic/amlogic,meson-gx-ao-secure.yaml#"
15 secure firmware.
22 const: amlogic,meson-gx-ao-secure
29 - const: amlogic,meson-gx-ao-secure
50 ao-secure@140 {
51 compatible = "amlogic,meson-gx-ao-secure", "syscon";
A Damlogic,meson-mx-secbus2.yaml16 The registers can be accessed directly when not running in "secure mode".
17 When "secure mode" is enabled then these registers have to be accessed
18 through secure monitor calls.
/linux-6.3-rc2/Documentation/devicetree/bindings/mailbox/
A Dti,secure-proxy.yaml4 $id: http://devicetree.org/schemas/mailbox/ti,secure-proxy.yaml#
13 The Texas Instruments' secure proxy is a mailbox controller that has
25 const: ti,am654-secure-proxy
30 Contains the secure proxy thread ID used for the specific transfer path.
48 secure proxy thread in the form 'rx_<PID>'.
54 Contains the interrupt information for the Rx interrupt path for secure
71 compatible = "ti,am654-secure-proxy";
/linux-6.3-rc2/Documentation/powerpc/
A Dultravisor.rst63 the VM it is returning to is secure.
102 that are running in secure mode can access secure memory.
161 passes control in secure mode.
243 When the secure pages are transferred back to secure memory, they may
473 of a secure virtual machine or if called from a
665 * U_INVALID if VM is not secure.
703 * U_INVALID if the VM is not secure.
752 * U_INVALID if VM is not secure.
766 yet, mark the PTE as secure and back it with a secure page when that
795 * U_INVAL if VM is not secure.
[all …]
/linux-6.3-rc2/Documentation/devicetree/bindings/arm/samsung/
A Dsamsung-secure-firmware.yaml4 $id: http://devicetree.org/schemas/arm/samsung/samsung-secure-firmware.yaml#
15 - const: samsung,secure-firmware
19 Address of non-secure SYSRAM used for communication with firmware.
31 compatible = "samsung,secure-firmware";
/linux-6.3-rc2/drivers/gpu/drm/amd/amdgpu/
A Damdgpu_ib.c139 bool secure; in amdgpu_ib_schedule() local
231 secure = false; in amdgpu_ib_schedule()
233 secure = ib->flags & AMDGPU_IB_FLAGS_SECURE; in amdgpu_ib_schedule()
234 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
241 if (secure != !!(ib->flags & AMDGPU_IB_FLAGS_SECURE)) { in amdgpu_ib_schedule()
242 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
243 secure = !secure; in amdgpu_ib_schedule()
244 amdgpu_ring_emit_frame_cntl(ring, true, secure); in amdgpu_ib_schedule()
253 amdgpu_ring_emit_frame_cntl(ring, false, secure); in amdgpu_ib_schedule()
/linux-6.3-rc2/Documentation/devicetree/bindings/nvmem/
A Dst,stm32-romem.yaml36 st,non-secure-otp:
38 This property explicits a factory programmed area that both secure
39 and non-secure worlds can access. It is needed when, by default, the
40 related area can only be reached by the secure world.
65 st,non-secure-otp;
A Damlogic-efuse.txt7 - secure-monitor: phandle to the secure-monitor node
20 secure-monitor = <&sm>;
35 sm: secure-monitor {
/linux-6.3-rc2/Documentation/devicetree/bindings/thermal/
A Damlogic,thermal.yaml31 amlogic,ao-secure:
32 description: phandle to the ao-secure syscon
43 - amlogic,ao-secure
56 amlogic,ao-secure = <&sec_AO>;
/linux-6.3-rc2/arch/arm/mach-omap2/
A DMakefile16 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-6.3-rc2/fs/
A Danon_inodes.c82 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-6.3-rc2/Documentation/devicetree/bindings/rng/
A Domap_rng.yaml17 - inside-secure,safexcel-eip76
50 - inside-secure,safexcel-eip76
75 compatible = "inside-secure,safexcel-eip76";
/linux-6.3-rc2/arch/s390/crypto/
A DKconfig22 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-6.3-rc2/Documentation/staging/
A Dtee.rst8 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.
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
214 building block for OP-TEE OS in secure world to implement the top half and
[all …]
/linux-6.3-rc2/arch/arm64/boot/dts/tesla/
A Dfsd.dtsi367 <GIC_SPI 439 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */
368 <GIC_SPI 451 IRQ_TYPE_LEVEL_HIGH>, /* Combined secure interrupt */
374 /* Per context non-secure context interrupts, 0-3 interrupts */
387 <GIC_SPI 322 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */
388 <GIC_SPI 346 IRQ_TYPE_LEVEL_HIGH>, /* Combined secure interrupt */
398 /* Per context non-secure context interrupts, 0-7 interrupts */
415 <GIC_SPI 196 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */
420 /* Per context non-secure context interrupts, 0-1 interrupts */
431 <GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>, /* Global non-secure fault */
432 <GIC_SPI 96 IRQ_TYPE_LEVEL_HIGH>, /* Combined secure interrupt */
[all …]
/linux-6.3-rc2/Documentation/devicetree/bindings/arm/tegra/
A Dnvidia,tegra194-cbb.yaml59 CCPLEX receives secure or nonsecure interrupt depending on error type.
60 A secure interrupt is received for SEC(firewall) & SLV errors and a
61 non-secure interrupt is received for TMO & DEC errors.
63 - description: non-secure interrupt
64 - description: secure interrupt
/linux-6.3-rc2/arch/powerpc/crypto/
A DKconfig51 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-6.3-rc2/arch/arm64/boot/dts/arm/
A Dcorstone1000.dtsi149 secure-status = "okay"; /* secure-world-only */
161 secure-status = "okay"; /* secure-world-only */
/linux-6.3-rc2/arch/mips/crypto/
A DKconfig39 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-6.3-rc2/Documentation/driver-api/firmware/
A Dother_interfaces.rst25 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-6.3-rc2/Documentation/devicetree/bindings/misc/
A Dbrcm,kona-smc.txt4 used for non-secure to secure communications.

Completed in 29 milliseconds

12345678910>>...14