Home
last modified time | relevance | path

Searched refs:interconnect (Results 1 – 25 of 79) sorted by relevance

1234

/Linux-v5.10/Documentation/devicetree/bindings/interconnect/
Dinterconnect.txt4 The purpose of this document is to define a common set of generic interconnect
8 = interconnect providers =
10 The interconnect provider binding is intended to represent the interconnect
11 controllers in the system. Each provider registers a set of interconnect
12 nodes, which expose the interconnect related capabilities of the interconnect
14 etc. The consumer drivers set constraints on interconnect path (or endpoints)
15 depending on the use case. Interconnect providers can also be interconnect
20 - compatible : contains the interconnect provider compatible string
21 - #interconnect-cells : number of cells in a interconnect specifier needed to
22 encode the interconnect node id and optionally add a
[all …]
/Linux-v5.10/Documentation/driver-api/
Dinterconnect.rst16 The interconnect bus is hardware with configurable parameters, which can be
18 An example of interconnect buses are the interconnects between various
22 Below is a simplified diagram of a real-world SoC interconnect bus topology.
55 Interconnect provider is the software definition of the interconnect hardware.
56 The interconnect providers on the above diagram are M NoC, S NoC, C NoC, P NoC
59 Interconnect node is the software definition of the interconnect hardware
60 port. Each interconnect provider consists of multiple interconnect nodes,
61 which are connected to other SoC components including other interconnect
63 called an interconnect node, which belongs to the Mem NoC interconnect provider.
70 include multiple master-slave pairs across several interconnect providers.
[all …]
/Linux-v5.10/drivers/interconnect/imx/
DMakefile1 imx-interconnect-objs := imx.o
2 imx8mm-interconnect-objs := imx8mm.o
3 imx8mq-interconnect-objs := imx8mq.o
4 imx8mn-interconnect-objs := imx8mn.o
6 obj-$(CONFIG_INTERCONNECT_IMX) += imx-interconnect.o
7 obj-$(CONFIG_INTERCONNECT_IMX8MM) += imx8mm-interconnect.o
8 obj-$(CONFIG_INTERCONNECT_IMX8MQ) += imx8mq-interconnect.o
9 obj-$(CONFIG_INTERCONNECT_IMX8MN) += imx8mn-interconnect.o
DKconfig2 tristate "i.MX interconnect drivers"
5 Generic interconnect drivers for i.MX SOCs
8 tristate "i.MX8MM interconnect driver"
12 tristate "i.MX8MN interconnect driver"
16 tristate "i.MX8MQ interconnect driver"
/Linux-v5.10/Documentation/devicetree/bindings/bus/
Dti-sysc.txt1 Texas Instruments sysc interconnect target module wrapper binding
3 Texas Instruments SoCs can have a generic interconnect target module
5 interconnect (Arteris NoC) and L4 interconnect (Sonics s3220). The sysc
8 of the interconnect.
10 Each interconnect target module can have one or more devices connected to
11 it. There is a set of control registers for managing interconnect target
12 module clocks, idle modes and interconnect level resets for the module.
15 space of the first child device IP block managed by the interconnect
43 - reg shall have register areas implemented for the interconnect
47 interconnect target module in question such as
[all …]
/Linux-v5.10/drivers/interconnect/qcom/
DKconfig3 bool "Qualcomm Network-on-Chip interconnect drivers"
6 Support for Qualcomm's Network-on-Chip interconnect hardware.
12 tristate "Qualcomm MSM8916 interconnect driver"
21 tristate "Qualcomm MSM8974 interconnect driver"
30 tristate "Qualcomm OSM L3 interconnect driver"
33 Say y here to support the Operating State Manager (OSM) interconnect
37 tristate "Qualcomm QCS404 interconnect driver"
49 tristate "Qualcomm SC7180 interconnect driver"
59 tristate "Qualcomm SDM845 interconnect driver"
69 tristate "Qualcomm SM8150 interconnect driver"
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/arm/omap/
Dl4.txt1 L4 interconnect bindings
3 These bindings describe the OMAP SoCs L4 interconnect bus.
19 - reg : registers link agent and interconnect agent and access protection
21 interconnect agent instances, "ap" for access if it exists
25 l4: interconnect@48000000 {
/Linux-v5.10/Documentation/devicetree/bindings/mmc/
Dsdhci-msm.txt58 * Following bus parameters are required for interconnect bandwidth scaling:
59 - interconnects: Pairs of phandles and interconnect provider specifier
61 the interconnect path.
63 - interconnect-names: For sdhc, we have two main paths.
66 For Data interconnect path the name supposed to be
67 is "sdhc-ddr" and for config interconnect path it is
70 interconnect/ for more details.
91 interconnect-names = "sdhc-ddr","cpu-sdhc";
/Linux-v5.10/Documentation/devicetree/bindings/arm/
Dcci.txt2 ARM CCI cache coherent interconnect binding description
6 cache coherent interconnect (CCI) that is capable of monitoring bus
14 * CCI interconnect node
20 through the CCI interconnect is the same as the one seen from the
51 CCI interconnect node can define the following child nodes:
56 Parent node must be CCI interconnect node.
85 Parent node must be CCI interconnect node.
124 * CCI interconnect bus masters
129 A CCI interconnect bus master node must contain the following
/Linux-v5.10/Documentation/devicetree/bindings/display/msm/
Ddpu.txt31 - interconnects : interconnect path specifier for MDSS according to
32 Documentation/devicetree/bindings/interconnect/interconnect.txt. Should be
34 - interconnect-names : MDSS will have 2 port names to differentiate between the
35 2 interconnect paths defined with interconnect specifier.
97 interconnect-names = "mdp0-mem", "mdp1-mem";
Dgpu.txt25 - interconnects: optional phandle to an interconnect provider. See
26 ../interconnect/interconnect.txt for details. Some A3xx and all A4xx platforms
28 - interconnect-names: The names of the interconnect paths that correspond to the
113 interconnect-names = "gfx-mem";
/Linux-v5.10/arch/arm64/boot/dts/qcom/
Dsc7180.dtsi14 #include <dt-bindings/interconnect/qcom,osm-l3.h>
15 #include <dt-bindings/interconnect/qcom,sc7180.h>
696 interconnect-names = "sdhc-ddr","cpu-sdhc";
760 interconnect-names = "qup-core";
776 interconnect-names = "qup-core", "qup-config",
795 interconnect-names = "qup-core", "qup-config";
811 interconnect-names = "qup-core", "qup-config";
828 interconnect-names = "qup-core", "qup-config",
847 interconnect-names = "qup-core", "qup-config";
863 interconnect-names = "qup-core", "qup-config";
[all …]
Dsm8150.dtsi14 #include <dt-bindings/interconnect/qcom,osm-l3.h>
444 config_noc: interconnect@1500000 {
447 #interconnect-cells = <1>;
451 system_noc: interconnect@1620000 {
454 #interconnect-cells = <1>;
458 mc_virt: interconnect@163a000 {
461 #interconnect-cells = <1>;
465 aggre1_noc: interconnect@16e0000 {
468 #interconnect-cells = <1>;
472 aggre2_noc: interconnect@1700000 {
[all …]
Dsm8250.dtsi10 #include <dt-bindings/interconnect/qcom,osm-l3.h>
1112 config_noc: interconnect@1500000 {
1115 #interconnect-cells = <1>;
1119 system_noc: interconnect@1620000 {
1122 #interconnect-cells = <1>;
1126 mc_virt: interconnect@163d000 {
1129 #interconnect-cells = <1>;
1133 aggre1_noc: interconnect@16e0000 {
1136 #interconnect-cells = <1>;
1140 aggre2_noc: interconnect@1700000 {
[all …]
/Linux-v5.10/drivers/interconnect/
DKconfig14 source "drivers/interconnect/imx/Kconfig"
15 source "drivers/interconnect/qcom/Kconfig"
/Linux-v5.10/Documentation/devicetree/bindings/clock/
Dti-clkctrl.txt4 interconnect target module. The clkctrl clock controller manages functional
8 interconnect target module on omap4 and later variants.
/Linux-v5.10/arch/arm/boot/dts/
Dam33xx.dtsi169 * XXX: Use a flat representation of the AM33XX interconnect.
170 * The real AM33XX interconnect network is quite complex. Since
182 l4_wkup: interconnect@44c00000 {
192 l4_per: interconnect@48000000 {
194 l4_fw: interconnect@47c00000 {
196 l4_fast: interconnect@4a000000 {
198 l4_mpuss: interconnect@4b140000 {
Dqcom-msm8974.dtsi4 #include <dt-bindings/interconnect/qcom,msm8974.h>
1348 bimc: interconnect@fc380000 {
1351 #interconnect-cells = <1>;
1357 snoc: interconnect@fc460000 {
1360 #interconnect-cells = <1>;
1366 pnoc: interconnect@fc468000 {
1369 #interconnect-cells = <1>;
1375 ocmemnoc: interconnect@fc470000 {
1378 #interconnect-cells = <1>;
1384 mmssnoc: interconnect@fc478000 {
[all …]
Ddra62x-clocks.dtsi18 /* Compared to dm814x, dra62x has interconnect clocks on isp PLL */
Domap5.dtsi137 * XXX: Use a flat representation of the OMAP3 interconnect.
138 * The real OMAP interconnect network is quite complex.
156 l4_wkup: interconnect@4ae00000 {
159 l4_cfg: interconnect@4a000000 {
162 l4_per: interconnect@48000000 {
165 l4_abe: interconnect@40100000 {
/Linux-v5.10/arch/arm64/boot/dts/nvidia/
Dtegra186.dtsi65 interconnect-names = "dma-mem", "write";
366 #interconnect-cells = <1>;
385 #interconnect-cells = <0>;
562 interconnect-names = "dma-mem", "write";
592 interconnect-names = "dma-mem", "write";
617 interconnect-names = "dma-mem", "write";
647 interconnect-names = "dma-mem", "write";
678 interconnect-names = "dma-mem", "write";
808 interconnect-names = "dma-mem", "write";
1033 interconnect-names = "dma-mem", "write";
[all …]
Dtegra194.dtsi64 interconnect-names = "dma-mem", "write";
406 #interconnect-cells = <1>;
440 #interconnect-cells = <0>;
707 interconnect-names = "dma-mem", "write";
733 interconnect-names = "dma-mem", "write";
764 interconnect-names = "dma-mem", "write";
795 interconnect-names = "dma-mem", "write";
1292 interconnect-names = "dma-mem";
1330 interconnect-names = "dma-mem", "read-1";
1348 interconnect-names = "dma-mem", "read-1";
[all …]
/Linux-v5.10/drivers/bus/
DKconfig21 interconnect for ARM platforms.
67 means of an embedded on top of the interconnect errors handler
123 Driver to enable OMAP interconnect error handling driver.
202 bool "TI sysc interconnect target module driver"
205 Generic driver for Texas Instruments interconnect target module
/Linux-v5.10/Documentation/devicetree/bindings/sound/
Domap-dmic.txt7 <L3 interconnect address, size>;
Domap-mcpdm.txt7 <L3 interconnect address, size>;

1234