Home
last modified time | relevance | path

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

12345678

/Linux-v5.10/Documentation/devicetree/bindings/arm/samsung/
Dsamsung-secure-firmware.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/arm/samsung/samsung-secure-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung Exynos Secure Firmware
10 - Krzysztof Kozlowski <krzk@kernel.org>
15 - const: samsung,secure-firmware
19 Address of non-secure SYSRAM used for communication with firmware.
23 - compatible
24 - reg
[all …]
/Linux-v5.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
11 firmware about the layout of the machine via devicetree.)
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
[all …]
/Linux-v5.10/drivers/firmware/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
7 menu "Firmware Drivers"
15 set of operating system-independent software interfaces that are
17 interfaces for: Discovery and self-description of the interfaces
19 a given device or domain into the various power-saving states that
37 enabled or disabled via the SCP firmware
51 provides a mechanism for inter-processor communication between SCP
70 enabled or disabled via the SCP firmware
77 standard for registering callbacks from the platform firmware
[all …]
Dstratix10-svc.c1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2017-2018, Intel Corporation
19 #include <linux/firmware/intel/stratix10-smc.h>
20 #include <linux/firmware/intel/stratix10-svc-client.h>
24 * SVC_NUM_DATA_IN_FIFO - number of struct stratix10_svc_data in the FIFO
26 * SVC_NUM_CHANNEL - number of channel supported by service layer driver
28 * FPGA_CONFIG_DATA_CLAIM_TIMEOUT_MS - claim back the submitted buffer(s)
29 * from the secure world for FPGA manager to reuse, or to free the buffer(s)
30 * when all bit-stream data had be send.
32 * FPGA_CONFIG_STATUS_TIMEOUT_SEC - poll the FPGA configuration status,
[all …]
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-secvar1 What: /sys/firmware/secvar
4 Description: This directory is created if the POWER firmware supports OS
5 secureboot, thereby secure variables. It exposes interface
6 for reading/writing the secure variables
8 What: /sys/firmware/secvar/vars
11 Description: This directory lists all the secure variables that are supported
12 by the firmware.
14 What: /sys/firmware/secvar/format
17 Description: A string indicating which backend is in use by the firmware.
21 What: /sys/firmware/secvar/vars/<variable name>
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/arm/amlogic/
Damlogic,meson-gx-ao-secure.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/arm/amlogic/amlogic,meson-gx-ao-secure.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
8 title: Amlogic Meson Firmware registers Interface
11 - Neil Armstrong <narmstrong@baylibre.com>
15 secure firmware.
22 const: amlogic,meson-gx-ao-secure
24 - compatible
29 - const: amlogic,meson-gx-ao-secure
[all …]
/Linux-v5.10/Documentation/driver-api/firmware/
Dother_interfaces.rst1 Other Firmware Interfaces
5 --------------
7 .. kernel-doc:: drivers/firmware/dmi_scan.c
11 --------------
13 .. kernel-doc:: drivers/firmware/edd.c
17 ---------------------------------
19 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).
29 .. kernel-doc:: include/linux/firmware/intel/stratix10-svc-client.h
[all …]
/Linux-v5.10/include/linux/firmware/intel/
Dstratix10-svc-client.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (C) 2017-2018, Intel Corporation
22 * Secure firmware accepts the request issued by one of service clients.
25 * Service client successfully submits data buffer to secure firmware.
28 * Secure firmware completes data process, ready to accept the
32 * Secure firmware completes service request successfully. In case of
42 * Secure firmware doesn't support requested features such as RSU retry
73 * enum stratix10_svc_command_code - supported service commands
75 * @COMMAND_NOOP: do 'dummy' request for integration/debug/trouble-shooting
80 * @COMMAND_RECONFIG_DATA_SUBMIT: submit buffer(s) of bit-stream data for the
[all …]
Dstratix10-smc.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (C) 2017-2018, Intel Corporation
9 #include <linux/arm-smccc.h>
13 * 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.
19 * An ARM SMC instruction takes a function identifier and up to 6 64-bit
20 * register values as arguments, and can return up to 4 64-bit register
21 * value. The operation of the secure monitor is determined by the parameter
[all …]
/Linux-v5.10/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.
72 * @NFC_CMD_FW_DOWNLOAD: Request to Load/flash firmware, or event to inform
73 * that some firmware was loaded
74 * @NFC_EVENT_SE_ADDED: Event emitted when a new secure element is discovered.
[all …]
/Linux-v5.10/arch/arm/mach-exynos/
Dfirmware.c1 // SPDX-License-Identifier: GPL-2.0
15 #include <asm/firmware.h>
16 #include <asm/hardware/cache-l2x0.h>
62 * because Exynos3250 removes WFE in secure mode. in exynos_cpu_boot()
79 return -ENODEV; in exynos_set_cpu_boot_addr()
84 * Almost all Exynos-series of SoCs that run in secure mode don't need in exynos_set_cpu_boot_addr()
100 return -ENODEV; in exynos_get_cpu_boot_addr()
159 * Before the cache can be enabled, due to firmware in exynos_l2_write_sec()
183 exynos_smc(SMC_CMD_L2X0SETUP1, regs->tag_latency, regs->data_latency, in exynos_l2_configure()
184 regs->prefetch_ctrl); in exynos_l2_configure()
[all …]
/Linux-v5.10/Documentation/admin-guide/
Dthunderbolt.rst1 .. SPDX-License-Identifier: GPL-2.0
10 connection manager can be implemented either in firmware or software.
11 Typically PCs come with a firmware connection manager for Thunderbolt 3
25 -----------------------------------
27 should be a userspace tool that handles all the low-level details, keeps
31 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
35 ``/etc/udev/rules.d/99-local.rules``::
53 All devices are automatically connected by the firmware. No user
63 secure
65 addition to UUID the device (if it supports secure connect) is sent
[all …]
/Linux-v5.10/drivers/firmware/meson/
Dmeson_sm.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Amlogic Secure Monitor driver
9 #define pr_fmt(fmt) "meson-sm: " fmt
11 #include <linux/arm-smccc.h>
23 #include <linux/firmware/meson/meson_sm.h>
62 const struct meson_sm_cmd *cmd = chip->cmd; in meson_sm_get_cmd()
64 while (cmd->smc_id && cmd->index != cmd_index) in meson_sm_get_cmd()
67 return cmd->smc_id; in meson_sm_get_cmd()
91 * meson_sm_call - generic SMC32 call to the secure-monitor
93 * @fw: Pointer to secure-monitor firmware
[all …]
/Linux-v5.10/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 -------------------
24 the firmware node.
26 - compatible: "intel,stratix10-svc" or "intel,agilex-svc"
27 - method: smc or hvc
28 smc - Secure Monitor Call
29 hvc - Hypervisor Call
[all …]
Dqcom,scm.txt1 QCOM Secure Channel Manager (SCM)
3 Qualcomm processors include an interface to communicate to the secure firmware.
5 can include CPU power up/down, HDCP requests, loading of firmware, and other
9 - compatible: must contain one of the following:
10 * "qcom,scm-apq8064"
11 * "qcom,scm-apq8084"
12 * "qcom,scm-ipq4019"
13 * "qcom,scm-ipq806x"
14 * "qcom,scm-ipq8074"
15 * "qcom,scm-msm8660"
[all …]
Dcznic,turris-mox-rwtm.txt1 Turris Mox rWTM firmware driver
4 - compatible : Should be "cznic,turris-mox-rwtm"
5 - mboxes : Must contain a reference to associated mailbox
8 compatible device running the Mox's rWTM firmware in the secure processor (for
9 example it is possible to flash this firmware into EspressoBin).
13 firmware {
14 turris-mox-rwtm {
15 compatible = "cznic,turris-mox-rwtm";
/Linux-v5.10/Documentation/arm/
Dfirmware.rst2 Interface for registering and calling firmware-specific operations for ARM
7 Some boards are running with secure firmware running in TrustZone secure
9 a need to provide an interface for such platforms to specify available firmware
12 Firmware operations can be specified by filling in a struct firmware_ops
18 The ops pointer must be non-NULL. More information about struct firmware_ops
19 and its members can be found in arch/arm/include/asm/firmware.h header.
22 set anything if platform does not require firmware operations.
24 To call a firmware operation, a helper macro is provided::
27 ((firmware_ops->op) ? firmware_ops->op(__VA_ARGS__) : (-ENOSYS))
30 -ENOSYS to signal that given operation is not available (for example, to allow
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/firmware/meson/
Dmeson_sm.txt1 * Amlogic Secure Monitor
3 In the Amlogic SoCs the Secure Monitor code is used to provide access to the
6 Required properties for the secure monitor node:
7 - compatible: Should be "amlogic,meson-gxbb-sm"
11 firmware {
12 sm: secure-monitor {
13 compatible = "amlogic,meson-gxbb-sm";
/Linux-v5.10/Documentation/devicetree/bindings/security/tpm/
Dgoogle,cr50.txt1 * H1 Secure Microcontroller with Cr50 Firmware on SPI Bus.
3 H1 Secure Microcontroller running Cr50 firmware provides several
4 functions, including TPM-like functionality. It communicates over
8 - compatible: Should be "google,cr50".
9 - spi-max-frequency: Maximum SPI frequency.
17 spi-max-frequency = <800000>;
/Linux-v5.10/drivers/staging/wfx/
Dhif_rx.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Implementation of chip-to-host event (aka indications) of WFxxx Split Mac
6 * Copyright (c) 2017-2020, Silicon Laboratories, Inc.
7 * Copyright (c) 2010, ST-Ericsson
25 int cmd = hif->id; in hif_generic_confirm()
26 int len = le16_to_cpu(hif->len) - 4; // drop header in hif_generic_confirm()
28 WARN(!mutex_is_locked(&wdev->hif_cmd.lock), "data locking error"); in hif_generic_confirm()
30 if (!wdev->hif_cmd.buf_send) { in hif_generic_confirm()
31 dev_warn(wdev->dev, "unexpected confirmation: 0x%.2x\n", cmd); in hif_generic_confirm()
32 return -EINVAL; in hif_generic_confirm()
[all …]
/Linux-v5.10/tools/testing/selftests/kexec/
Dkexec_common_lib.sh2 # SPDX-License-Identifier: GPL-2.0
6 VERBOSE="${VERBOSE:-1}"
7 IKCONFIG="/tmp/config-`uname -r`"
8 KERNEL_IMAGE="/boot/vmlinuz-`uname -r`"
13 [ $VERBOSE -ne 0 ] && echo "[INFO] $1"
19 [ $VERBOSE -ne 0 ] && echo "$1 [PASS]"
26 [ $VERBOSE -ne 0 ] && echo "$1 [FAIL]"
33 [ $VERBOSE -ne 0 ] && echo "$1"
37 # Check efivar SecureBoot-$(the UUID) and SetupMode-$(the UUID).
38 # (Based on kdump-lib.sh)
[all …]
/Linux-v5.10/Documentation/virt/kvm/
Damd-memory-encryption.rst2 Secure Encrypted Virtualization (SEV)
8 Secure Encrypted Virtualization (SEV) is a feature found on AMD processors.
10 SEV is an extension to the AMD-V architecture which supports running
44 Hence, the ASID for the SEV-enabled guests must be from 1 to a maximum value
51 Secure Processor (AMD-SP). Firmware running inside the AMD-SP provides a secure
54 information, see the SEV Key Management spec [api-spec]_
60 likely return ``EFAULT``). If non-NULL, the argument to KVM_MEMORY_ENCRYPT_OP
77 are defined in ``<linux/psp-dev.h>``.
83 ---------------
88 Returns: 0 on success, -negative on error
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/timer/
Darm,arch_timer.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marc Zyngier <marc.zyngier@arm.com>
11 - Mark Rutland <mark.rutland@arm.com>
13 ARM cores may have a per-core architected timer, which provides per-cpu timers,
17 The per-core architected timer is attached to a GIC to deliver its
18 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
24 - items:
25 - enum:
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/arm/firmware/
Dtlm,trusted-foundations.txt2 -------------------
4 Boards that use the Trusted Foundations secure monitor can signal its
5 presence by declaring a node compatible with "tlm,trusted-foundations"
6 under the /firmware/ node
9 - compatible: "tlm,trusted-foundations"
10 - tlm,version-major: major version number of Trusted Foundations firmware
11 - tlm,version-minor: minor version number of Trusted Foundations firmware
14 firmware {
15 trusted-foundations {
16 compatible = "tlm,trusted-foundations";
[all …]
/Linux-v5.10/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
164 This selects the ASPEED Secure Digital Host Controller Interface.
197 This selects the Secure Digital Host Controller Interface (SDHCI)
[all …]

12345678