| /OK3568_Linux_fs/u-boot/arch/arm/cpu/armv8/ |
| H A D | Kconfig | 4 bool "Enable multiple CPUs to enter into U-Boot"
9 Say Y here if there is not any trust firmware to set
10 CPUECTLR_EL1.SMPEN bit before U-Boot.
17 register may be controlled by EL3/EL2 firmware. To be more
18 precise, by default (if there is EL2/EL3 firmware running)
25 bool "Support spin-table enable method"
28 Say Y here to support "spin-table" enable method for booting Linux.
31 - Specify enable-method = "spin-table" in each CPU node in the
33 - Bring secondary CPUs into U-Boot proper in a board specific
38 U-Boot automatically does:
[all …]
|
| H A D | sec_firmware.c | 4 * SPDX-License-Identifier: GPL-2.0+
23 * Secure firmware load addr
24 * Flags used: 0x1 secure firmware has been loaded to secure memory
25 * 0x2 secure firmware is running
30 #define SEC_FIRMWARE_FIT_IMAGE "firmware"
51 printf("SEC Firmware: %s: no such config\n", conf_node_name); in sec_firmware_get_data()
52 return -ENOENT; in sec_firmware_get_data()
58 printf("SEC Firmware: No '%s' in config\n", in sec_firmware_get_data()
60 return -ENOLINK; in sec_firmware_get_data()
63 /* Verify secure firmware image */ in sec_firmware_get_data()
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/firmware/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/samsung/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/amlogic/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/firmware/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/include/linux/firmware/intel/ |
| H A 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 …]
|
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-exynos/ |
| H A 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 …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/linux/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/include/uapi/linux/ |
| H A 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 …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/linux/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/drivers/firmware/meson/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/arm/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/firmware/ |
| H A 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 …]
|
| H A D | qcom,scm.txt | 1 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 …]
|
| /OK3568_Linux_fs/buildroot/board/qemu/arm-vexpress-tz/ |
| H A D | readme.txt | 1 Board qemu_arm_vexpress_tz builds a QEMU ARMv7-A target system with
2 OP-TEE running in the TrustZone secure world and a Linux based
3 OS running in the non-secure world. The board configuration enables
9 The BIOS used in the QEMU host is the ARM Trusted Firmware-A (TF-A).
10 In our configuration, U-Boot uses QEMU semihosting file access to load the
14 cd output/images && ../host/bin/qemu-system-arm \
15 -machine virt -machine secure=on -cpu cortex-a15 \
16 -smp 1 -s -m 1024 -d unimp \
17 -serial stdio \
18 -netdev user,id=vmnic -device virtio-net-device,netdev=vmnic \
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/staging/wfx/ |
| H A D | hif_rx.c | 1 // 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/security/tpm/ |
| H A 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>;
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/kexec/ |
| H A D | kexec_common_lib.sh | 2 # 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 …]
|
| /OK3568_Linux_fs/u-boot/arch/arm/cpu/armv7/ |
| H A D | Kconfig | 13 bool "Enable support for booting in non-secure mode" if EXPERT
16 ---help---
17 Say Y here to enable support for booting in non-secure / SVC mode.
20 bool "Boot in secure mode by default" if EXPERT
23 ---help---
24 Say Y here to boot in secure mode by default even if non-secure mode
26 suppport booting in non-secure mode. Only set this if you need it.
27 This can be overridden at run-time by setting the bootm_boot_mode env.
34 ---help---
35 Say Y here to boot in hypervisor (HYP) mode when booting non-secure.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/firmware/meson/ |
| H A 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";
|