Home
last modified time | relevance | path

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

12345678910>>...12

/linux/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/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/Documentation/devicetree/bindings/iommu/
A 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>;
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/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/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/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/drivers/gpu/drm/amd/amdgpu/
A Damdgpu_ib.c139 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/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/Documentation/devicetree/bindings/nvmem/
A Dst,stm32-romem.yaml32 st,non-secure-otp:
34 This property explicits a factory programmed area that both secure
35 and non-secure worlds can access. It is needed when, by default, the
36 related area can only be reached by the secure world.
61 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/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/Documentation/devicetree/bindings/rng/
A Domap_rng.yaml17 - inside-secure,safexcel-eip76
50 - inside-secure,safexcel-eip76
61 - inside-secure,safexcel-eip76
86 compatible = "inside-secure,safexcel-eip76";
/linux/arch/arm/mach-omap2/
A DMakefile19 secure-common = omap-smc.o omap-secure.o
22 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
23 obj-$(CONFIG_ARCH_OMAP4) += $(secure-common)
24 obj-$(CONFIG_SOC_AM33XX) += $(secure-common)
25 obj-$(CONFIG_SOC_OMAP5) += $(secure-common)
26 obj-$(CONFIG_SOC_AM43XX) += $(secure-common)
27 obj-$(CONFIG_SOC_DRA7XX) += $(secure-common)
/linux/arch/arm/crypto/
A 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
107 Use a faster and more secure NEON based implementation of AES in CBC,
/linux/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/Documentation/ABI/testing/
A 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
/linux/Documentation/driver-api/firmware/
A 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/drivers/vfio/
A DKconfig7 VFIO provides a framework for secure userspace device drivers.
37 considered secure. VFIO No-IOMMU mode enables IOMMU groups for
39 infrastructure in a non-secure mode. Use of this mode will result
/linux/Documentation/devicetree/bindings/firmware/meson/
A Dmeson_sm.txt6 Required properties for the secure monitor node:
12 sm: secure-monitor {
/linux/Documentation/devicetree/bindings/misc/
A Dbrcm,kona-smc.txt4 used for non-secure to secure communications.
/linux/Documentation/devicetree/bindings/timer/
A Dti,timer.txt32 - ti,timer-secure: Indicates the timer is reserved on a secure OMAP device
43 ti,timer-secure;
/linux/drivers/of/
A 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/Documentation/devicetree/bindings/firmware/
A 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

Completed in 28 milliseconds

12345678910>>...12