Home
last modified time | relevance | path

Searched full:interconnect (Results 1 – 25 of 754) sorted by relevance

12345678910>>...31

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/interconnect/
Dinterconnect.txt1 Interconnect Provider Device Tree Bindings
4 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
[all …]
Dqcom,qcs404.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,qcs404.yaml#
7 title: Qualcomm QCS404 Network-On-Chip interconnect
13 The Qualcomm QCS404 interconnect providers support adjusting the
26 '#interconnect-cells':
42 - '#interconnect-cells'
52 bimc: interconnect@400000 {
55 #interconnect-cells = <1>;
61 pnoc: interconnect@500000 {
64 #interconnect-cells = <1>;
70 snoc: interconnect@580000 {
[all …]
Dqcom,msm8916.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8916.yaml#
7 title: Qualcomm MSM8916 Network-On-Chip interconnect
13 The Qualcomm MSM8916 interconnect providers support adjusting the
26 '#interconnect-cells':
42 - '#interconnect-cells'
52 bimc: interconnect@400000 {
55 #interconnect-cells = <1>;
61 pcnoc: interconnect@500000 {
64 #interconnect-cells = <1>;
70 snoc: interconnect@580000 {
[all …]
Dqcom,rpmh.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,rpmh.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect
14 RPMh interconnect providers support system bandwidth requirements through
71 '#interconnect-cells':
78 this interconnect to send RPMh commands.
88 - '#interconnect-cells'
95 #include <dt-bindings/interconnect/qcom,sdm845.h>
97 mem_noc: interconnect@1380000 {
100 #interconnect-cells = <1>;
104 mmss_noc: interconnect@1740000 {
[all …]
Dqcom,osm-l3.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,osm-l3.yaml#
7 title: Qualcomm Operating State Manager (OSM) L3 Interconnect Provider
14 The OSM L3 interconnect provider aggregates the L3 bandwidth requests
38 '#interconnect-cells':
46 - '#interconnect-cells'
56 osm_l3: interconnect@17d41000 {
63 #interconnect-cells = <1>;
Dqcom,msm8974.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8974.yaml#
7 title: Qualcomm MSM8974 Network-On-Chip Interconnect
13 The Qualcomm MSM8974 interconnect providers support setting system
29 '#interconnect-cells':
45 - '#interconnect-cells'
55 bimc: interconnect@fc380000 {
58 #interconnect-cells = <1>;
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interconnect/
Dinterconnect.txt1 Interconnect Provider Device Tree Bindings
4 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
[all …]
Dqcom,qcm2290.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,qcm2290.yaml#
7 title: Qualcomm QCM2290 Network-On-Chip interconnect
13 The Qualcomm QCM2290 interconnect providers support adjusting the
26 '#interconnect-cells':
41 '^interconnect-[a-z0-9]+$':
44 The interconnect providers do not have a separate QoS register space,
54 '#interconnect-cells':
69 - '#interconnect-cells'
78 - '#interconnect-cells'
88 snoc: interconnect@1880000 {
[all …]
Dqcom,sm6350-rpmh.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,sm6350-rpmh.yaml#
7 title: Qualcomm SM6350 RPMh Network-On-Chip Interconnect
13 Qualcomm RPMh-based interconnect provider on SM6350.
33 '#interconnect-cells': true
36 '^interconnect-[a-z0-9\-]+$':
39 The interconnect providers do not have a separate QoS register space,
49 '#interconnect-cells': true
64 config_noc: interconnect@1500000 {
67 #interconnect-cells = <2>;
71 system_noc: interconnect@1620000 {
[all …]
Dqcom,rpm.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,rpm.yaml#
7 title: Qualcomm RPM Network-On-Chip Interconnect
13 RPM interconnect providers support system bandwidth requirements through
47 '#interconnect-cells':
49 Value: <1> is one cell in an interconnect specifier for the
50 interconnect node id, <2> requires the interconnect node id and an
67 '^interconnect-[a-z0-9]+$':
78 '#interconnect-cells':
93 - '#interconnect-cells'
100 - '#interconnect-cells'
[all …]
Dqcom,qdu1000-rpmh.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,qdu1000-rpmh.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect on QDU1000
14 RPMh interconnect providers support system bandwidth requirements through
29 '#interconnect-cells': true
57 #include <dt-bindings/interconnect/qcom,qdu1000-rpmh.h>
59 system_noc: interconnect@1640000 {
62 #interconnect-cells = <2>;
66 clk_virt: interconnect-0 {
68 #interconnect-cells = <2>;
Dqcom,sc7280-rpmh.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,sc7280-rpmh.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect on SC7280
14 RPMh interconnect providers support system bandwidth requirements through
17 See also:: include/dt-bindings/interconnect/qcom,sc7280.h
60 interconnect {
62 #interconnect-cells = <2>;
66 interconnect@9100000 {
69 #interconnect-cells = <2>;
Dqcom,msm8974.yaml4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8974.yaml#
7 title: Qualcomm MSM8974 Network-On-Chip Interconnect
13 The Qualcomm MSM8974 interconnect providers support setting system
29 '#interconnect-cells':
45 - '#interconnect-cells'
55 bimc: interconnect@fc380000 {
58 #interconnect-cells = <1>;
/kernel/linux/linux-5.10/Documentation/driver-api/
Dinterconnect.rst4 Generic System Interconnect Subsystem
16 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.
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/
Dinterconnect.rst4 Generic System Interconnect Subsystem
16 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.
[all …]
/kernel/linux/linux-6.6/drivers/interconnect/qcom/
DKconfig3 tristate "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 MSM8939 interconnect driver"
30 tristate "Qualcomm MSM8974 interconnect driver"
39 tristate "Qualcomm MSM8996 interconnect driver"
48 tristate "Qualcomm OSM L3 interconnect driver"
51 Say y here to support the Operating State Manager (OSM) interconnect
55 tristate "Qualcomm QCM2290 interconnect driver"
64 tristate "Qualcomm QCS404 interconnect driver"
[all …]
/kernel/linux/linux-5.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 …]
Dbaikal,bt1-axi.yaml16 cores. Traffic arbitration is done by means of DW AXI Interconnect (so
17 called AXI Main Interconnect) routing IO requests from one block to
22 (Errors Handler Block) embedded on top of the DW AXI Interconnect and
36 - description: Synopsys DesignWare AXI Interconnect QoS registers
45 '#interconnect-cells':
57 - description: Main Interconnect uplink reference clock
65 - description: Main Interconnect reset line
93 #interconnect-cells = <1>;
/kernel/linux/linux-6.6/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
5 imx8mp-interconnect-objs := imx8mp.o
7 obj-$(CONFIG_INTERCONNECT_IMX) += imx-interconnect.o
8 obj-$(CONFIG_INTERCONNECT_IMX8MM) += imx8mm-interconnect.o
9 obj-$(CONFIG_INTERCONNECT_IMX8MQ) += imx8mq-interconnect.o
10 obj-$(CONFIG_INTERCONNECT_IMX8MN) += imx8mn-interconnect.o
11 obj-$(CONFIG_INTERCONNECT_IMX8MP) += imx8mp-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"
20 tristate "i.MX8MP interconnect driver"
/kernel/linux/linux-5.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"
60 tristate "Qualcomm SC7180 interconnect driver"
69 tristate "Qualcomm SDM845 interconnect driver"
78 tristate "Qualcomm SM8150 interconnect driver"
[all …]
/kernel/linux/linux-5.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
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/bus/
Dti-sysc.yaml7 title: Texas Instruments interconnect target module
13 Texas Instruments SoCs can have a generic interconnect target module
14 for devices connected to various interconnects such as L3 interconnect
15 using Arteris NoC, and L4 interconnect using Sonics s3220. This module
18 than that it is mostly independent of the interconnect.
20 Each interconnect target module can have one or more devices connected to
21 it. There is a set of control registers for managing the interconnect target
22 module clocks, idle modes and interconnect level resets.
24 The interconnect target module control registers are sprinkled into the
26 the interconnect target module. Typically the register names are REVISION,
[all …]
/kernel/linux/linux-6.6/drivers/interconnect/
DKconfig2 menuconfig INTERCONNECT config
3 bool "On-Chip Interconnect management support"
12 if INTERCONNECT
14 source "drivers/interconnect/imx/Kconfig"
15 source "drivers/interconnect/qcom/Kconfig"
16 source "drivers/interconnect/samsung/Kconfig"
22 Support for wrapping clocks into the interconnect nodes.
/kernel/linux/linux-6.6/drivers/net/ipa/
Dipa_power.c9 #include <linux/interconnect.h>
60 * @interconnect_count: Number of elements in interconnect[]
61 * @interconnect: Interconnect array
70 struct icc_bulk_data interconnect[]; member
77 struct icc_bulk_data *interconnect; in ipa_interconnect_init() local
81 /* Initialize our interconnect data array for bulk operations */ in ipa_interconnect_init()
82 interconnect = &power->interconnect[0]; in ipa_interconnect_init()
84 /* interconnect->path is filled in by of_icc_bulk_get() */ in ipa_interconnect_init()
85 interconnect->name = data->name; in ipa_interconnect_init()
86 interconnect->avg_bw = data->average_bandwidth; in ipa_interconnect_init()
[all …]

12345678910>>...31