Home
last modified time | relevance | path

Searched +full:tightly +full:- +full:coupled (Results 1 – 25 of 43) sorted by relevance

12

/kernel/linux/linux-5.10/arch/csky/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
119 In kernel we parse the *regs->pc to determine whether to send SIGTRAP or not.
162 # VA_BITS - PAGE_SHIFT - 3
196 prompt "C-SKY PMU type"
226 bool "Tightly-Coupled/Sram Memory"
229 The implementation are not only used by TCM (Tightly-Coupled Meory)
232 re-used directly.
276 bool "Symmetric Multi-Processing (SMP) support for C-SKY"
281 int "Maximum number of CPUs (2-32)"
296 hex "DRAM start addr (the same with memory-section in dts)"
[all …]
/kernel/linux/linux-4.19/Documentation/arm/
Dtcm.txt1 ARM TCM (Tightly-Coupled Memory) handling in Linux
2 ----
5 Some ARM SoC:s have a so-called TCM (Tightly-Coupled Memory).
6 This is usually just a few (4-64) KiB of RAM inside the ARM
10 Harvard-architecture, so there is an ITCM (instruction TCM)
22 determine if ITCM (bits 1-0) and/or DTCM (bit 17-16) is present
50 - FIQ and other interrupt handlers that need deterministic
53 - Idle loops where all external RAM is set to self-refresh
54 retention mode, so only on-chip RAM is accessible by
58 - Other operations which implies shutting off or reconfiguring
[all …]
D00-INDEX1 00-INDEX
2 - this file
4 - requirements for booting
6 - Cache Coherent Network ring-bus and perf PMU driver.
8 - ARM Interrupt subsystem documentation
10 - Intel IXP4xx Network processor.
12 - Netwinder specific documentation
14 - Symbol definitions for porting Linux to a new ARM machine.
16 - Kernel initialization parameters on ARM Linux
18 - General ARM documentation
[all …]
/kernel/linux/linux-5.10/Documentation/arm/
Dtcm.rst2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
8 This is usually just a few (4-64) KiB of RAM inside the ARM
12 Harvard-architecture, so there is an ITCM (instruction TCM)
24 determine if ITCM (bits 1-0) and/or DTCM (bit 17-16) is present
52 - FIQ and other interrupt handlers that need deterministic
55 - Idle loops where all external RAM is set to self-refresh
56 retention mode, so only on-chip RAM is accessible by
60 - Other operations which implies shutting off or reconfiguring
66 - Define the physical address and size of ITCM and DTCM.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt3 The NVIC provides an interrupt controller that is tightly coupled to
4 Cortex-M based processor cores. The NVIC implemented on different SoCs
9 - compatible : should be one of:
10 "arm,v6m-nvic"
11 "arm,v7m-nvic"
12 "arm,v8m-nvic"
13 - interrupt-controller : Identifies the node as an interrupt controller
14 - #interrupt-cells : Specifies the number of cells needed to encode an
21 - reg : Specifies base physical address(s) and size of the NVIC registers.
24 - arm,num-irq-priority-bits: The number of priority bits implemented by the
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt3 The NVIC provides an interrupt controller that is tightly coupled to
4 Cortex-M based processor cores. The NVIC implemented on different SoCs
9 - compatible : should be one of:
10 "arm,v6m-nvic"
11 "arm,v7m-nvic"
12 "arm,v8m-nvic"
13 - interrupt-controller : Identifies the node as an interrupt controller
14 - #interrupt-cells : Specifies the number of cells needed to encode an
21 - reg : Specifies base physical address(s) and size of the NVIC registers.
24 - arm,num-irq-priority-bits: The number of priority bits implemented by the
[all …]
/kernel/linux/linux-5.10/Documentation/sound/soc/
Doverview.rst6 provide better ALSA support for embedded system-on-chip processors (e.g.
9 had some limitations:-
11 * Codec drivers were often tightly coupled to the underlying SoC
12 CPU. This is not ideal and leads to code duplication - for example,
18 machine specific code to re-route audio, enable amps, etc., after such an
31 features :-
54 multiple re-usable component drivers :-
/kernel/linux/linux-4.19/Documentation/sound/soc/
Doverview.rst6 provide better ALSA support for embedded system-on-chip processors (e.g.
9 had some limitations:-
11 * Codec drivers were often tightly coupled to the underlying SoC
12 CPU. This is not ideal and leads to code duplication - for example,
18 machine specific code to re-route audio, enable amps, etc., after such an
31 features :-
54 multiple re-usable component drivers :-
/kernel/linux/linux-5.10/drivers/cpuidle/
Dcoupled.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * coupled.c - helper functions to enter the same idle state on multiple cpus
21 * DOC: Coupled cpuidle states
30 * WFI), and one or more "coupled" power states that affect blocks
32 * sometimes the whole SoC). Entering a coupled power state must
33 * be tightly controlled on both cpus.
36 * WFI state until all cpus are ready to enter a coupled state, at
37 * which point the coupled state function will be called on all
46 * ready counter matches the number of online coupled cpus. If any
50 * requested_state stores the deepest coupled idle state each cpu
[all …]
/kernel/linux/linux-4.19/drivers/cpuidle/
Dcoupled.c2 * coupled.c - helper functions to enter the same idle state on multiple cpus
30 * DOC: Coupled cpuidle states
39 * WFI), and one or more "coupled" power states that affect blocks
41 * sometimes the whole SoC). Entering a coupled power state must
42 * be tightly controlled on both cpus.
45 * WFI state until all cpus are ready to enter a coupled state, at
46 * which point the coupled state function will be called on all
55 * ready counter matches the number of online coupled cpus. If any
59 * requested_state stores the deepest coupled idle state each cpu
65 * and only read after all the cpus are ready for the coupled idle
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/leds/
Dcommon.txt10 have to be tightly coupled with the LED device binding. They are represented
14 - led-sources : List of device current outputs the LED is connected to. The
17 - label : The label for this LED. If omitted, the label is taken from the node
22 - default-state : The initial state of the LED. Valid values are "on", "off",
23 and "keep". If the LED is already on or off and the default-state property is
29 - linux,default-trigger : This parameter, if present, is a
31 "backlight" - LED will act as a back-light, controlled by the framebuffer
33 "default-on" - LED will turn on (but for leds-gpio see "default-state"
34 property in Documentation/devicetree/bindings/leds/leds-gpio.txt)
35 "heartbeat" - LED "double" flashes at a load average based rate
[all …]
/kernel/linux/linux-4.19/drivers/bus/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
28 Driver for the Broadcom Set Top Box System-on-a-chip internal bus
53 cores. This bus is for per-CPU tightly coupled devices such as the
95 tristate "Simple Power-Managed Bus Driver"
156 with the peripherals in the FPGA of the TS-4600 SoM.
164 needed to use on-board devices connected to UniPhier SoCs.
184 source "drivers/bus/fsl-mc/Kconfig"
/kernel/linux/linux-5.10/arch/arm/include/asm/
Dcp15.h1 /* SPDX-License-Identifier: GPL-2.0 */
14 #define CR_P (1 << 4) /* 32-bit exception handler */
15 #define CR_D (1 << 5) /* 32-bit data address range */
55 extern unsigned long cr_alignment; /* defined in entry-armv.S */
107 * cr_alignment is tightly coupled to cp15 (at least in the minds of the
109 * read-only) is fine for most cases and saves quite some #ifdeffery.
/kernel/linux/linux-5.10/drivers/media/platform/mtk-vpu/
Dmtk_vpu.h1 /* SPDX-License-Identifier: GPL-2.0-only */
4 * Author: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
23 * enum ipi_id - the id of inter-processor interrupt
65 * enum rst_id - reset id to register reset function for VPU watchdog timeout
80 * vpu_ipi_register - register an ipi function
96 * vpu_ipi_send - send data from AP to vpu.
103 * This function is thread-safe. When this function returns,
115 * vpu_get_plat_device - get VPU's platform device
126 * vpu_wdt_reg_handler - register a VPU watchdog handler
144 * vpu_get_vdec_hw_capa - get video decoder hardware capability
[all …]
Dmtk_vpu.c1 // SPDX-License-Identifier: GPL-2.0-only
4 * Author: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
18 #include <linux/dma-mapping.h>
32 /* maximum program/data TCM (Tightly-Coupled Memory) size */
63 /* vpu inter-processor communication interrupt */
67 * enum vpu_fw_type - VPU firmware type
79 * struct vpu_mem - VPU extended program/data memory information
91 * struct vpu_regs - VPU TCM and configuration registers
93 * @tcm: the register for VPU Tightly-Coupled Memory
104 * struct vpu_wdt_handler - VPU watchdog reset handler
[all …]
/kernel/linux/linux-4.19/drivers/soc/qcom/
Dllcc-sdm845.c1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (c) 2017-2018, The Linux Foundation. All rights reserved.
11 #include <linux/soc/qcom/llcc-qcom.h>
27 * slice: normal or TCM(Tightly Coupled Memory)
80 { .compatible = "qcom,sdm845-llcc", },
86 .name = "sdm845-llcc",
/kernel/linux/linux-4.19/arch/arm/include/asm/
Dcp15.h1 /* SPDX-License-Identifier: GPL-2.0 */
14 #define CR_P (1 << 4) /* 32-bit exception handler */
15 #define CR_D (1 << 5) /* 32-bit data address range */
73 extern unsigned long cr_alignment; /* defined in entry-armv.S */
125 * cr_alignment is tightly coupled to cp15 (at least in the minds of the
127 * read-only) is fine for most cases and saves quite some #ifdeffery.
/kernel/linux/linux-4.19/drivers/media/platform/mtk-vpu/
Dmtk_vpu.h3 * Author: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
31 * enum ipi_id - the id of inter-processor interrupt
73 * enum rst_id - reset id to register reset function for VPU watchdog timeout
88 * vpu_ipi_register - register an ipi function
104 * vpu_ipi_send - send data from AP to vpu.
111 * This function is thread-safe. When this function returns,
123 * vpu_get_plat_device - get VPU's platform device
134 * vpu_wdt_reg_handler - register a VPU watchdog handler
152 * vpu_get_vdec_hw_capa - get video decoder hardware capability
161 * vpu_get_venc_hw_capa - get video encoder hardware capability
[all …]
Dmtk_vpu.c3 * Author: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
26 #include <linux/dma-mapping.h>
40 /* maximum program/data TCM (Tightly-Coupled Memory) size */
69 /* vpu inter-processor communication interrupt */
73 * enum vpu_fw_type - VPU firmware type
85 * struct vpu_mem - VPU extended program/data memory information
97 * struct vpu_regs - VPU TCM and configuration registers
99 * @tcm: the register for VPU Tightly-Coupled Memory
110 * struct vpu_wdt_handler - VPU watchdog reset handler
121 * struct vpu_wdt - VPU watchdog workqueue
[all …]
/kernel/linux/linux-5.10/drivers/bus/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
37 Driver for the Broadcom Set Top Box System-on-a-chip internal bus
42 bool "Baikal-T1 APB-bus driver"
46 Baikal-T1 AXI-APB bridge is used to access the SoC subsystem CSRs.
53 errors counter. The counter and the APB-bus operations timeout can be
57 bool "Baikal-T1 AXI-bus driver"
61 AXI3-bus is the main communication bus connecting all high-speed
62 peripheral IP-cores with RAM controller and with MIPS P5600 cores on
63 Baikal-T1 SoC. Traffic arbitration is done by means of DW AMBA 3 AXI
103 cores. This bus is for per-CPU tightly coupled devices such as the
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/
Dcommon.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
21 have to be tightly coupled with the LED device binding. They are represented
25 led-sources:
30 $ref: /schemas/types.yaml#definitions/uint32-array
35 from the header include/dt-bindings/leds/common.h. If there is no
42 the header include/dt-bindings/leds/common.h. If there is no matching
[all …]
/kernel/linux/linux-4.19/Documentation/power/regulator/
Dconsumer.txt11 A consumer driver can get access to its supply regulator by calling :-
20 To release the regulator the consumer driver should call :-
25 analog and digital supplies :-
37 A consumer can enable its power supply by calling:-
45 A consumer can determine if a regulator is enabled by calling :-
52 A consumer can disable its supply when no longer needed by calling :-
59 Finally, a regulator can be forcefully disabled in the case of an emergency :-
75 Consumers can control their supply voltage by calling :-
87 The regulators configured voltage output can be found by calling :-
105 Consumers can control their supply current limit by calling :-
[all …]
/kernel/linux/linux-5.10/Documentation/power/regulator/
Dconsumer.rst144 --------------------------------
163 ------------------------------
165 Bespoke or tightly coupled drivers may want to directly control regulator
199 they need to do low-level hardware access to regulators, with no involvement
202 - clocksource with a voltage-controlled oscillator and control logic to change
204 - thermal management firmware that can issue an arbitrary I2C transaction to
212 Bus-specific details, like I2C addresses or transfer rates are handled by the
225 regulator_list_voltage) to a hardware-specific voltage selector that can be
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/
Dti,k3-r5f-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-r5f-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The TI K3 family of SoCs usually have one or more dual-core Arm Cortex R5F
20 Each Dual-Core R5F sub-system is represented as a single DTS node
33 - ti,am654-r5fss
34 - ti,j721e-r5fss
36 power-domains:
[all …]
/kernel/linux/linux-5.10/drivers/clk/imx/
Dclk-scu.c1 // SPDX-License-Identifier: GPL-2.0+
7 #include <dt-bindings/firmware/imx/rsrc.h>
8 #include <linux/arm-smccc.h>
9 #include <linux/clk-provider.h>
13 #include "clk-scu.h"
21 * struct clk_scu - Description of one SCU clock
33 * struct imx_sc_msg_req_set_clock_rate - clock set rate protocol
58 * struct imx_sc_msg_get_clock_rate - clock get rate protocol
74 * struct imx_sc_msg_get_clock_parent - clock get parent protocol
95 * struct imx_sc_msg_set_clock_parent - clock set parent protocol
[all …]

12