| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-secure-firmware.yaml | 1 # 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 1 * 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 …]
|
| /kernel/linux/linux-5.10/drivers/firmware/ |
| D | Kconfig | 1 # 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 …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-secvar | 1 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/amlogic/ |
| D | amlogic,meson-gx-ao-secure.yaml | 1 # 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 …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 1 * 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/firmware/ |
| D | other_interfaces.rst | 1 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 …]
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ |
| D | base.c | 24 * Secure boot is the process by which NVIDIA-signed firmware is loaded into
26 * for the firmware to access useful (but sensitive) registers.
31 * - Non-secure (NS). In this mode, functionality is similar to Falcon
32 * architectures before security modes were introduced (pre-Maxwell), but
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
[all …]
|
| /kernel/linux/linux-5.10/include/linux/firmware/intel/ |
| D | stratix10-svc-client.h | 1 /* 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 …]
|
| D | stratix10-smc.h | 1 /* 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 …]
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | nfc.h | 33 * 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 …]
|
| /kernel/linux/linux-4.19/include/uapi/linux/ |
| D | nfc.h | 33 * 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 …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-boards.txt | 4 - compatible = should be one or more of the following.
5 - "samsung,aries" - for S5PV210-based Samsung Aries board.
6 - "samsung,fascinate4g" - for S5PV210-based Samsung Galaxy S Fascinate 4G (SGH-T959P) board.
7 - "samsung,galaxys" - for S5PV210-based Samsung Galaxy S (i9000) board.
8 - "samsung,artik5" - for Exynos3250-based Samsung ARTIK5 module.
9 - "samsung,artik5-eval" - for Exynos3250-based Samsung ARTIK5 eval board.
10 - "samsung,monk" - for Exynos3250-based Samsung Simband board.
11 - "samsung,rinato" - for Exynos3250-based Samsung Gear2 board.
12 - "samsung,smdkv310" - for Exynos4210-based Samsung SMDKV310 eval board.
13 - "samsung,trats" - for Exynos4210-based Tizen Reference board.
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-exynos/ |
| D | firmware.c | 1 // 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 …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-exynos/ |
| D | firmware.c | 1 // 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 …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/ |
| D | thunderbolt.rst | 5 should be a userspace tool that handles all the low-level details, keeps
9 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
13 ``/etc/udev/rules.d/99-local.rules``::
22 -----------------------------------
33 All devices are automatically connected by the firmware. No user
43 secure
45 addition to UUID the device (if it supports secure connect) is sent
51 The firmware automatically creates tunnels for Display Port and
56 The firmware automatically creates tunnels for the USB controller and
65 If the security level reads as ``user`` or ``secure`` the connected
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | thunderbolt.rst | 1 .. 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 …]
|
| /kernel/linux/linux-5.10/drivers/firmware/meson/ |
| D | meson_sm.c | 1 // 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/firmware/ |
| D | intel,stratix10-svc.txt | 3 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 …]
|
| /kernel/linux/linux-4.19/Documentation/arm/ |
| D | firmware.txt | 1 Interface for registering and calling firmware-specific operations for ARM.
2 ----
5 Some boards are running with secure firmware running in TrustZone secure
7 a need to provide an interface for such platforms to specify available firmware
10 Firmware operations can be specified by filling in a struct firmware_ops
16 The ops pointer must be non-NULL. More information about struct firmware_ops
17 and its members can be found in arch/arm/include/asm/firmware.h header.
20 set anything if platform does not require firmware operations.
22 To call a firmware operation, a helper macro is provided
25 ((firmware_ops->op) ? firmware_ops->op(__VA_ARGS__) : (-ENOSYS))
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | firmware.rst | 2 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 …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/firmware/meson/ |
| D | meson_sm.txt | 1 * 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";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/firmware/meson/ |
| D | meson_sm.txt | 1 * 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";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/security/tpm/ |
| D | google,cr50.txt | 1 * 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>;
|
| /kernel/linux/linux-4.19/arch/arm/firmware/ |
| D | Kconfig | 8 menu "Firmware options"
12 bool "Trusted Foundations secure monitor support"
16 Some devices (including most Tegra-based consumer devices on the
17 market) are booted with the Trusted Foundations secure monitor
18 active, requiring some core operations to be performed by the secure
21 This option allows the kernel to invoke the secure monitor whenever
24 tlm,trusted-foundations device tree binding documentation for details
|