Home
last modified time | relevance | path

Searched full:secure (Results 1 – 25 of 1376) sorted by relevance

12345678910>>...56

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Dsecure.txt1 * ARM Secure world bindings
4 "Normal" and "Secure". Most devicetree consumers (including the Linux
6 world or the Secure world. However some devicetree consumers are
8 visible only in the Secure address space, only in the Normal address
10 virtual machine which boots Secure firmware and wants to tell the
13 The general principle of the naming scheme for Secure world bindings
14 is that any property that needs a different value in the Secure world
15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
17 a vendor prefix, the Secure variant of "vendor,foo" would be
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/
Dsecure.txt1 * ARM Secure world bindings
4 "Normal" and "Secure". Most devicetree consumers (including the Linux
6 world or the Secure world. However some devicetree consumers are
8 visible only in the Secure address space, only in the Normal address
10 virtual machine which boots Secure firmware and wants to tell the
13 The general principle of the naming scheme for Secure world bindings
14 is that any property that needs a different value in the Secure world
15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
17 a vendor prefix, the Secure variant of "vendor,foo" would be
[all …]
/kernel/linux/linux-5.10/Documentation/powerpc/
Dultravisor.rst15 POWER 9 that enables Secure Virtual Machines (SVMs). DD2.3 chips
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.
73 **Secure Mode MSR Settings**
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
[all …]
/kernel/linux/linux-5.10/arch/powerpc/kvm/
Dbook3s_hv_uvmem.c3 * Secure pages management: Migration of pages between normal and secure
10 * A pseries guest can be run as secure guest on Ultravisor-enabled
13 * hypervisor (HV) and secure memory managed by Ultravisor (UV).
18 * Private ZONE_DEVICE memory equal to the amount of secure memory
19 * available in the platform for running secure guests is hotplugged.
20 * Whenever a page belonging to the guest becomes secure, a page from this
21 * private device memory is used to represent and track that secure page
36 * UV(secure) and vice versa. So the serialization points are around
40 * fault path as page-out can occur when HV faults on accessing secure
44 * by HV touching secure pages is very very low. If an when UV supports
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/crypto/
Dinside-secure-safexcel.txt1 Inside Secure SafeXcel cryptographic engine
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";
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/crypto/
Dinside-secure-safexcel.txt1 Inside Secure SafeXcel cryptographic engine
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";
/kernel/linux/linux-4.19/arch/s390/include/uapi/asm/
Dpkey.h23 #define SECKEYBLOBSIZE 64 /* secure key blob size is always 64 bytes */
32 /* Struct to hold a secure key blob */
34 __u8 seckey[SECKEYBLOBSIZE]; /* the secure key blob */
50 * Generate secure key
56 struct pkey_seckey seckey; /* out: the secure key blob */
61 * Construct secure key from clear key value
68 struct pkey_seckey seckey; /* out: the secure key blob */
73 * Fabricate protected key from a secure key
78 struct pkey_seckey seckey; /* in: the secure key blob */
95 * Verification Pattern provided inside a secure key.
[all …]
/kernel/linux/linux-4.19/arch/s390/include/asm/
Dpkey.h19 * Generate (AES) random secure key.
23 * @param seckey pointer to buffer receiving the secure key
30 * Generate (AES) secure key with given key value.
35 * @param seckey pointer to buffer receiving the secure key
43 * Derive (AES) proteced key from the (AES) secure key blob.
46 * @param seckey pointer to buffer with the input secure key
69 * Verification Pattern provided inside a secure key.
70 * @param seckey pointer to buffer with the input secure key
82 * Find card and transform secure key to protected key.
83 * @param seckey pointer to buffer with the input secure key
[all …]
/kernel/linux/linux-4.19/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>;
/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>;
/kernel/linux/linux-4.19/arch/arm/common/
Dsecure_cntvoff.S5 * Initialization of CNTVOFF register from secure mode
15 * CNTVOFF has to be initialized either from non-secure Hypervisor
16 * mode or secure Monitor mode with SCR.NS==1. If TrustZone is enabled
17 * then it should be handled by the secure code. The CPU must implement
21 mrc p15, 0, r1, c1, c1, 0 /* Get Secure Config */
23 mcr p15, 0, r0, c1, c1, 0 /* Set Non Secure bit */
28 mcr p15, 0, r1, c1, c1, 0 /* Set Secure bit */
/kernel/linux/linux-5.10/arch/arm/common/
Dsecure_cntvoff.S5 * Initialization of CNTVOFF register from secure mode
15 * CNTVOFF has to be initialized either from non-secure Hypervisor
16 * mode or secure Monitor mode with SCR.NS==1. If TrustZone is enabled
17 * then it should be handled by the secure code. The CPU must implement
21 mrc p15, 0, r1, c1, c1, 0 /* Get Secure Config */
23 mcr p15, 0, r0, c1, c1, 0 /* Set Non Secure bit */
28 mcr p15, 0, r1, c1, c1, 0 /* Set Secure bit */
/kernel/linux/linux-5.10/include/net/
Dmacsec.h103 * struct macsec_rx_sa - receive secure association
108 * @ssci: short secure channel identifier
137 * struct macsec_rx_sc - receive secure channel
138 * @sci: secure channel identifier for this SC
140 * @sa: array of secure associations
154 * struct macsec_tx_sa - transmit secure association
159 * @ssci: short secure channel identifier
177 * struct macsec_tx_sc - transmit secure channel
184 * @sa: array of secure associations
201 * @n_rx_sc: number of receive secure channels configured on this SecY
[all …]
/kernel/linux/linux-4.19/arch/arm/mach-omap2/
Domap-secure.h2 * omap-secure.h: OMAP Secure infrastructure header.
24 /* Secure HAL API flags */
31 /* Maximum Secure memory storage size */
36 /* Secure low power HAL API index */
42 /* Secure Monitor mode APIs */
53 /* Secure PPA(Primary Protected Application) APIs */
57 /* Secure RX-51 PPA (Primary Protected Application) APIs */
Domap-smc.S2 * OMAP34xx and OMAP44xx secure APIs file.
18 * This is common routine to manage secure monitor API
19 * used to modify the PL310 secure registers.
38 * Low level common routine for secure HAL and PPA APIs.
50 mov r12, #0x00 @ Secure Service ID
61 * Low level common routine for secure HAL and PPA APIs via smc #1
62 * r0 - @service_id: Secure Service ID
69 mov r12, r0 @ Copy the secure service ID
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Domap-secure.h3 * omap-secure.h: OMAP Secure infrastructure header.
23 /* Secure HAL API flags */
30 /* Maximum Secure memory storage size */
35 /* Secure low power HAL API index */
41 /* Secure Monitor mode APIs */
52 /* Secure PPA(Primary Protected Application) APIs */
60 /* Secure RX-51 PPA (Primary Protected Application) APIs */
Domap-smc.S3 * OMAP34xx and OMAP44xx secure APIs file.
15 * This is common routine to manage secure monitor API
16 * used to modify the PL310 secure registers.
36 * Low level common routine for secure HAL and PPA APIs.
48 mov r12, #0x00 @ Secure Service ID
59 * Low level common routine for secure HAL and PPA APIs via smc #1
60 * r0 - @service_id: Secure Service ID
67 mov r12, r0 @ Copy the secure service ID
Domap-secure.c3 * OMAP Secure API infrastructure.
23 #include "omap-secure.h"
50 * omap_sec_dispatcher: Routine to dispatch low power secure
55 * @arg1, arg2, arg3 args4: Parameters passed to secure API
72 * Secure API needs physical address in omap_secure_dispatcher()
88 WARN(res.a0, "Secure function call 0x%08x failed\n", fn); in omap_smccc_smc()
103 /* Allocate the memory to save secure ram */
141 * rx51_secure_dispatcher: Routine to dispatch secure PPA API calls
146 * @arg1, arg2, arg3 args4: Parameters passed to secure API
166 * Secure API needs physical address in rx51_secure_dispatcher()
[all …]
/kernel/linux/linux-5.10/drivers/tee/optee/
Doptee_smc.h75 * Used by non-secure world to figure out which Trusted OS is installed.
88 * Used by non-secure world to figure out which version of the Trusted OS
155 * Returns the Secure/Non-secure shared memory config.
187 * Exchanges capabilities between normal world and secure world
197 * a1 bitfield of secure world capabilities OPTEE_SMC_SEC_CAP_*
202 * a1 bitfield of secure world capabilities OPTEE_SMC_SEC_CAP_*
207 /* Secure world has reserved shared memory for normal world to use */
209 /* Secure world can communicate via previously unregistered shared memory */
213 * Secure world supports commands "register/unregister shared memory",
214 * secure world accepts command buffers located in any parts of non-secure RAM
[all …]
/kernel/linux/linux-5.10/arch/s390/include/uapi/asm/
Dpkey.h23 #define SECKEYBLOBSIZE 64 /* secure key blob size is always 64 bytes */
78 /* Struct to hold a CCA AES secure key blob */
80 __u8 seckey[SECKEYBLOBSIZE]; /* the secure key blob */
110 * Generate CCA AES secure key.
116 struct pkey_seckey seckey; /* out: the secure key blob */
121 * Construct CCA AES secure key from clear key value
128 struct pkey_seckey seckey; /* out: the secure key blob */
133 * Fabricate AES protected key from a CCA AES secure key
138 struct pkey_seckey seckey; /* in: the secure key blob */
155 * Verification Pattern provided inside a CCA AES secure key.
[all …]
/kernel/linux/linux-4.19/drivers/gpu/drm/nouveau/nvkm/subdev/secboot/
Dbase.c24 * Secure boot is the process by which NVIDIA-signed firmware is loaded into
31 * - Non-secure (NS). In this mode, functionality is similar to Falcon
38 * - Heavy Secure (HS). In this mode, the microprocessor is a black box - it's
42 * (The loading process involves tagging the IMEM block as secure, writing the
46 * - Light Secure (LS). In this mode, the microprocessor has more privileges
52 * Secure boot consists in temporarily switching a HS-capable falcon (typically
54 * load them, and switch managed falcons into LS mode. Once secure boot
57 * Secure boot requires a write-protected memory region (WPR) which can only be
58 * written by the secure falcon. On dGPU, the driver sets up the WPR region in
62 * The secure boot process takes place as follows:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/amlogic/
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";
/kernel/linux/linux-5.10/include/linux/firmware/intel/
Dstratix10-smc.h13 * This file defines the Secure Monitor Call (SMC) message protocol used for
14 * service layer driver in normal world (EL1) to communicate with secure
15 * monitor software in Secure Monitor Exception Level 3 (EL3).
17 * This file is shared with secure firmware (FW) which is out of kernel tree.
21 * value. The operation of the secure monitor is determined by the parameter
31 * STD call starts a operation which can be preempted by a non-secure
54 * Secure monitor software doesn't recognize the request.
57 * Secure monitor software accepts the service client's request.
60 * Secure monitor software is still processing service client's request.
63 * Secure monitor software reject the service client's request.
[all …]
/kernel/linux/linux-5.10/include/uapi/linux/
Dnfc.h67 * @NFC_CMD_ENABLE_SE: Enable the physical link to a specific secure element.
68 * Once enabled a secure element will handle card emulation mode, i.e.
69 * starting a poll from a device which has a secure element enabled means
71 * @NFC_CMD_DISABLE_SE: Disable the physical link to a specific secure element.
74 * @NFC_EVENT_SE_ADDED: Event emitted when a new secure element is discovered.
77 * @NFC_EVENT_SE_REMOVED: Event emitted when a secure element is removed from
79 * @NFC_EVENT_SE_CONNECTIVITY: This event is emitted whenever a secure element
87 * @NFC_CMD_GET_SE: Dump all discovered secure elements from an NFC controller.
88 * @NFC_CMD_SE_IO: Send/Receive APDUs to/from the selected secure element.
154 * @NFC_ATTR_SE: Available Secure Elements
[all …]
/kernel/linux/linux-4.19/include/uapi/linux/
Dnfc.h67 * @NFC_CMD_ENABLE_SE: Enable the physical link to a specific secure element.
68 * Once enabled a secure element will handle card emulation mode, i.e.
69 * starting a poll from a device which has a secure element enabled means
71 * @NFC_CMD_DISABLE_SE: Disable the physical link to a specific secure element.
74 * @NFC_EVENT_SE_ADDED: Event emitted when a new secure element is discovered.
77 * @NFC_EVENT_SE_REMOVED: Event emitted when a secure element is removed from
79 * @NFC_EVENT_SE_CONNECTIVITY: This event is emitted whenever a secure element
87 * @NFC_CMD_GET_SE: Dump all discovered secure elements from an NFC controller.
88 * @NFC_CMD_SE_IO: Send/Receive APDUs to/from the selected secure element.
154 * @NFC_ATTR_SE: Available Secure Elements
[all …]

12345678910>>...56