Home
last modified time | relevance | path

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

12345678

/kernel/linux/linux-5.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"
12 sm: secure-monitor {
13 compatible = "amlogic,meson-gxbb-sm";
/kernel/linux/linux-5.10/include/linux/firmware/intel/
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 …]
/kernel/linux/linux-6.6/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 */
40 return -ENODEV; in bcm_kona_smc_init()
45 return -EINVAL; in bcm_kona_smc_init()
49 return -ENOMEM; in bcm_kona_smc_init()
52 pr_info("Kona Secure API initialized\n"); in bcm_kona_smc_init()
60 * Only core 0 can run the secure monitor code. If an "smc" request
67 * cache and interrupt handling while the secure monitor executes.
69 * Parameters to the "smc" request are passed in r4-r6 as follows:
[all …]
/kernel/linux/linux-5.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>
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
109 if (!fw->chip) in meson_sm_call()
[all …]
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # Amlogic Secure Monitor driver
10 Say y here to enable the Amlogic secure monitor driver
/kernel/linux/linux-6.6/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>
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
109 if (!fw->chip) in meson_sm_call()
[all …]
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
/kernel/linux/linux-5.10/arch/arm/mach-bcm/
Dbcm_kona_smc.c37 {.compatible = "brcm,kona-smc"},
38 {.compatible = "bcm,kona-smc"}, /* deprecated name */
54 return -ENODEV; in bcm_kona_smc_init()
59 return -EINVAL; in bcm_kona_smc_init()
61 /* We assume space for four 32-bit arguments */ in bcm_kona_smc_init()
63 return -EINVAL; in bcm_kona_smc_init()
68 return -EINVAL; in bcm_kona_smc_init()
72 return -ENOMEM; in bcm_kona_smc_init()
75 pr_info("Kona Secure API initialized\n"); in bcm_kona_smc_init()
83 * Only core 0 can run the secure monitor code. If an "smc" request
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/nvmem/
Damlogic-efuse.txt4 - compatible: should be "amlogic,meson-gxbb-efuse"
5 - clocks: phandle to the efuse peripheral clock provided by the
7 - secure-monitor: phandle to the secure-monitor node
16 compatible = "amlogic,meson-gxbb-efuse";
18 #address-cells = <1>;
19 #size-cells = <1>;
20 secure-monitor = <&sm>;
35 sm: secure-monitor {
36 compatible = "amlogic,meson-gxbb-sm";
46 nvmem-cells = <&eth_mac>;
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/nvmem/
Damlogic,meson-gxbb-efuse.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/amlogic,meson-gxbb-efuse.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Neil Armstrong <neil.armstrong@linaro.org>
13 - $ref: nvmem.yaml#
18 - const: amlogic,meson-gxbb-efuse
19 - items:
20 - const: amlogic,meson-gx-efuse
21 - const: amlogic,meson-gxbb-efuse
[all …]
/kernel/linux/linux-6.6/include/linux/firmware/intel/
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 …]
/kernel/linux/linux-5.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 -------------------
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 …]
/kernel/linux/linux-6.6/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 …]
Damlogic,meson-gxbb-sm.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/amlogic,meson-gxbb-sm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Amlogic Secure Monitor (SM)
10 In the Amlogic SoCs the Secure Monitor code is used to provide access to the
14 - Neil Armstrong <neil.armstrong@linaro.org>
19 - const: amlogic,meson-gxbb-sm
20 - items:
21 - const: amlogic,meson-gx-sm
[all …]
/kernel/linux/linux-6.6/drivers/firmware/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
19 provides a mechanism for inter-processor communication between SCP
70 bool "Add firmware-provided memory map to sysfs" if EXPERT
73 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
77 See also Documentation/ABI/testing/sysfs-firmware-memmap.
110 DMI-based module auto-loading.
182 and manages secure monitor call to communicate with secure monitor
183 software at secure monitor exception level.
222 warm-restart enter a special debug mode that allows the user to
[all …]
/kernel/linux/linux-5.10/drivers/firmware/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
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
51 provides a mechanism for inter-processor communication between SCP
103 bool "Add firmware-provided memory map to sysfs" if EXPERT
106 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
110 See also Documentation/ABI/testing/sysfs-firmware-memmap.
143 DMI-based module auto-loading.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
Damlogic,meson-sec-pwrc.yaml1 # SPDX-License-Identifier: (GPL-2.0+ OR MIT)
5 ---
6 $id: "http://devicetree.org/schemas/power/amlogic,meson-sec-pwrc.yaml#"
7 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
9 title: Amlogic Meson Secure Power Domains
12 - Jianxin Pan <jianxin.pan@amlogic.com>
15 Secure Power Domains used in Meson A1/C1 SoCs, and should be the child node
16 of secure-monitor.
21 - amlogic,meson-a1-pwrc
23 "#power-domain-cells":
[all …]
/kernel/linux/linux-6.6/arch/arm/mach-omap2/
Domap-secure.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * omap-secure.h: OMAP Secure infrastructure header.
15 /* Monitor error code */
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.
18 * the monitor API number. It uses few CPU 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}
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/
Damlogic,meson-sec-pwrc.yaml1 # SPDX-License-Identifier: (GPL-2.0+ OR MIT)
5 ---
6 $id: http://devicetree.org/schemas/power/amlogic,meson-sec-pwrc.yaml#
7 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 title: Amlogic Meson Secure Power Domains
12 - Jianxin Pan <jianxin.pan@amlogic.com>
15 Secure Power Domains used in Meson A1/C1/S4 & C3 SoCs, and should be the child node
16 of secure-monitor.
21 - amlogic,meson-a1-pwrc
22 - amlogic,meson-s4-pwrc
[all …]
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Domap-secure.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * omap-secure.h: OMAP Secure infrastructure header.
15 /* Monitor error code */
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.
18 * the monitor API number. It uses few CPU 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}
[all …]
/kernel/linux/linux-6.6/arch/arm/mach-highbank/
Dsmc.S1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copied from omap44xx-smc.S Copyright (C) 2010 Texas Instruments, Inc.
10 * This is common routine to manage secure monitor API
11 * used to modify the PL310 secure registers.
13 * the monitor API number.
16 .arch armv7-a
19 stmfd sp!, {r4-r11, lr}
24 ldmfd sp!, {r4-r11, pc}
/kernel/linux/linux-5.10/arch/arm/mach-highbank/
Dsmc.S1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copied from omap44xx-smc.S Copyright (C) 2010 Texas Instruments, Inc.
10 * This is common routine to manage secure monitor API
11 * used to modify the PL310 secure registers.
13 * the monitor API number.
16 .arch armv7-a
19 stmfd sp!, {r4-r11, lr}
24 ldmfd sp!, {r4-r11, pc}
/kernel/linux/linux-5.10/arch/arm/common/
Dsecure_cntvoff.S1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Initialization of CNTVOFF register from secure mode
13 .arch armv7-a
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 */

12345678