Home
last modified time | relevance | path

Searched +full:secure +full:- +full:only (Results 1 – 25 of 639) sorted by relevance

12345678910>>...26

/Linux-v6.1/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 …]
/Linux-v6.1/Documentation/powerpc/
Dultravisor.rst1 .. SPDX-License-Identifier: GPL-2.0
15 POWER 9 that enables Secure Virtual Machines (SVMs). DD2.3 chips
16 (PVR=0x004e1203) or greater will be PEF-capable. A new ISA release
25 +------------------+
29 +------------------+
31 +------------------+
33 +------------------+
35 +------------------+
38 VMs in the system. SVMs are protected while at rest and can only be
56 process is running in secure mode, MSR(S) bit 41. MSR(S)=1, process
[all …]
/Linux-v6.1/arch/s390/include/uapi/asm/
Dpkey.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
23 #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 */
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/nvmem/
Dst,stm32-romem.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/st,stm32-romem.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectronics STM32 Factory-programmed data bindings
10 This represents STM32 Factory-programmed read only non-volatile area: locked
11 flash, OTP, read-only HW regs... This contains various information such as:
16 - Fabrice Gasnier <fabrice.gasnier@foss.st.com>
19 - $ref: "nvmem.yaml#"
24 - st,stm32f4-otp
[all …]
/Linux-v6.1/arch/arm/mach-omap2/
Domap-secure.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * OMAP Secure API infrastructure.
11 #include <linux/arm-smccc.h>
23 #include "omap-secure.h"
39 * We only check that the OP-TEE node is present and available. The in omap_optee_init_check()
40 * OP-TEE kernel driver is not needed for the type of interaction made in omap_optee_init_check()
41 * with OP-TEE here so the driver's status is not checked. in omap_optee_init_check()
50 * omap_sec_dispatcher: Routine to dispatch low power secure
55 * @arg1, arg2, arg3 args4: Parameters passed to secure API
57 * Return the non-zero error value on failure.
[all …]
Domap-secure.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * 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.S1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * OMAP34xx and OMAP44xx secure APIs file.
15 * This is common routine to manage secure monitor API
16 * used to modify the PL310 secure registers.
23 .arch armv7-a
26 stmfd sp!, {r2-r12, lr}
31 ldmfd sp!, {r2-r12, pc}
36 * Low level common routine for secure HAL and PPA APIs.
43 stmfd sp!, {r4-r12, lr}
48 mov r12, #0x00 @ Secure Service ID
[all …]
/Linux-v6.1/include/uapi/linux/
Dnfc.h33 * enum nfc_commands - supported nfc commands
62 * a device. LTO must be set before the link is up otherwise -EINPROGRESS
65 * If one of the passed parameters is wrong none is set and -EINVAL is
67 * @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
[all …]
/Linux-v6.1/drivers/s390/crypto/
Dzcrypt_ccamisc.h1 /* SPDX-License-Identifier: GPL-2.0+ */
17 #define TOKTYPE_NON_CCA 0x00 /* Non-CCA key token */
41 /* inside view of a CCA secure key token (only type 0x01 version 0x04) */
81 /* AES-128 512 640 */
82 /* AES-192 576 640 */
83 /* AES-256 640 640 */
97 /* inside view of an CCA secure ECC private key */
107 u8 htype; /* hash method, 0x02 for SHA-256 */
133 * Simple check if the token is a valid CCA secure AES data key
141 * Simple check if the token is a valid CCA secure AES cipher key
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/mailbox/
Dti,secure-proxy.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,secure-proxy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments' Secure Proxy
10 - Nishanth Menon <nm@ti.com>
13 The Texas Instruments' secure proxy is a mailbox controller that has
16 called "threads" or "proxies" - each instance is unidirectional and is
22 pattern: "^mailbox@[0-9a-f]+$"
25 const: ti,am654-secure-proxy
[all …]
/Linux-v6.1/drivers/tee/optee/
Doptee_rpc_cmd.h1 /* SPDX-License-Identifier: BSD-2-Clause */
3 * Copyright (c) 2016-2021, Linaro Limited
12 * Only the commands handled by the kernel driver are defined here.
14 * RPC communication with tee-supplicant is reversed compared to normal
23 * 1970-01-01 00:00:00 +0000 (UTC).
31 * Notification from/to secure world.
33 * If secure world needs to wait for something, for instance a mutex, it
34 * does a notification wait request instead of spinning in secure world.
35 * Conversely can a synchronous notification can be sent when a secure
39 * which instead is sent via a non-secure interrupt.
[all …]
Doptee_smc.h1 /* SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) */
3 * Copyright (c) 2015-2021, Linaro Limited
8 #include <linux/arm-smccc.h>
28 * Normal cached memory (write-back), shareable for SMP systems and not
36 * 32-bit registers.
44 * 384fb3e0-e7f8-11e3-af63-0002a5d5c51b.
75 * Used by non-secure world to figure out which Trusted OS is installed.
78 * Returns UUID in a0-4 in the same way as OPTEE_SMC_CALLS_UID
88 * Used by non-secure world to figure out which version of the Trusted OS
92 * Returns revision in a0-1 in the same way as OPTEE_SMC_CALLS_REVISION
[all …]
/Linux-v6.1/arch/arm/mach-bcm/
Dbcm_kona_smc.c1 // SPDX-License-Identifier: GPL-2.0-only
25 {.compatible = "brcm,kona-smc"},
26 {.compatible = "bcm,kona-smc"}, /* deprecated name */
42 return -ENODEV; in bcm_kona_smc_init()
47 return -EINVAL; in bcm_kona_smc_init()
49 /* We assume space for four 32-bit arguments */ in bcm_kona_smc_init()
51 return -EINVAL; in bcm_kona_smc_init()
56 return -EINVAL; in bcm_kona_smc_init()
60 return -ENOMEM; in bcm_kona_smc_init()
63 pr_info("Kona Secure API initialized\n"); in bcm_kona_smc_init()
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/iommu/
Dqcom,iommu.txt3 Qualcomm "B" family devices which are not compatible with arm-smmu have
6 to non-secure vs secure interrupt line.
10 - compatible : Should be one of:
12 "qcom,msm8916-iommu"
14 Followed by "qcom,msm-iommu-v1".
16 - clock-names : Should be a pair of "iface" (required for IOMMUs
20 - clocks : Phandles for respective clocks described by
21 clock-names.
23 - #address-cells : must be 1.
25 - #size-cells : must be 1.
[all …]
/Linux-v6.1/Documentation/staging/
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
14 - Registration of TEE drivers
16 - Managing shared memory between Linux and the TEE
18 - Providing a generic API to the TEE
25 User space (the client) connects to the driver by opening /dev/tee[0-9]* or
26 /dev/teepriv[0-9]*.
28 - TEE_IOC_SHM_ALLOC allocates shared memory and returns a file descriptor
34 - TEE_IOC_VERSION lets user space know which TEE this driver handles and
37 - TEE_IOC_OPEN_SESSION opens a new session to a Trusted Application.
[all …]
/Linux-v6.1/Documentation/virt/kvm/s390/
Ds390-pv.rst1 .. SPDX-License-Identifier: GPL-2.0
8 -------
15 Each guest starts in non-protected mode and then may make a request to
20 The Ultravisor will secure and decrypt the guest's boot memory
33 -------------------
46 safeguarding; they can only be injected for instructions that have
54 -------------------------------
64 ---------------------
70 The control structures associated with SIE provide the Secure
72 Secure Interception General Register Save Area. Guest GRs and most of
[all …]
/Linux-v6.1/net/sunrpc/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
20 tristate "Secure RPC: Kerberos V mechanism"
27 Choose Y here to enable Secure RPC using the Kerberos version 5
28 GSS-API mechanism (RFC 1964).
30 Secure RPC calls with Kerberos require an auxiliary user-space
31 daemon which may be found in the Linux nfs-utils package
32 available from http://linux-nfs.org/. In addition, user-space
38 bool "Secure RPC: Disable insecure Kerberos encryption types"
43 with the Kerberos version 5 GSS-API mechanism (RFC 1964). The
44 deprecated encryption types include DES-CBC-MD5, DES-CBC-CRC,
[all …]
/Linux-v6.1/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
38 Description: A read-only file containing the value of the variable. The size
44 Description: A write-only file that is used to submit the new value for the
/Linux-v6.1/include/net/
Dmacsec.h1 /* SPDX-License-Identifier: GPL-2.0+ */
62 * struct macsec_key - SA key
63 * @id: user-provided key identifier
118 * struct macsec_rx_sa - receive secure association
123 * @ssci: short secure channel identifier
124 * @stats: per-SA stats
152 * struct macsec_rx_sc - receive secure channel
153 * @sci: secure channel identifier for this SC
155 * @sa: array of secure associations
156 * @stats: per-SC stats
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/firmware/
Dintel,stratix10-svc.txt3 Intel Stratix10 SoC is composed of a 64 bit quad-core ARM Cortex A53 hard
4 processor system (HPS) and Secure Device Manager (SDM). When the FPGA is
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
22 -------------------
26 - compatible: "intel,stratix10-svc" or "intel,agilex-svc"
27 - method: smc or hvc
28 smc - Secure Monitor Call
29 hvc - Hypervisor Call
30 - memory-region:
[all …]
/Linux-v6.1/drivers/firmware/meson/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # Amlogic Secure Monitor driver
6 tristate "Amlogic Secure Monitor driver"
11 Say y here to enable the Amlogic secure monitor driver
/Linux-v6.1/drivers/mmc/host/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
59 tristate "Secure Digital Host Controller Interface support"
62 This selects the generic Secure Digital Host Controller Interface.
85 implements a hardware byte swapper using a 32-bit datum.
99 This selects the PCI Secure Digital Host Controller Interface.
114 disabled, it will steal the MMC cards away - rendering them
137 This selects the common helper functions support for Secure Digital
151 This selects the Arasan Secure Digital Host Controller Interface
165 This selects the ASPEED Secure Digital Host Controller Interface.
179 option only if you will boot the kernel for the purpose of running
[all …]
/Linux-v6.1/arch/powerpc/kvm/
Dbook3s_hv_uvmem.c1 // SPDX-License-Identifier: GPL-2.0
3 * 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).
15 * The page-in or page-out requests from UV will come to HV as hcalls and
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
31 * kvm->arch.uvmem_lock is a per-guest lock that prevents concurrent
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/rng/
Domap_rng.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: OMAP SoC and Inside-Secure HWRNG Module
10 - Jayesh Choudhary <j-choudhary@ti.com>
15 - ti,omap2-rng
16 - ti,omap4-rng
17 - inside-secure,safexcel-eip76
33 - description: EIP150 gatable clock
34 - description: Main gatable clock
[all …]
/Linux-v6.1/drivers/vfio/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "VFIO Non-Privileged userspace driver framework"
8 VFIO provides a framework for secure userspace device drivers.
9 See Documentation/driver-api/vfio.rst for more details.
34 bool "VFIO No-IOMMU support"
37 Only with an IOMMU can userspace access to DMA capable devices be
38 considered secure. VFIO No-IOMMU mode enables IOMMU groups for
39 devices without IOMMU backing for the purpose of re-using the VFIO
40 infrastructure in a non-secure mode. Use of this mode will result
50 source "drivers/vfio/fsl-mc/Kconfig"

12345678910>>...26