/linux/Documentation/devicetree/bindings/interconnect/ |
H A D | interconnect.txt | 1 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 …]
|
H A D | qcom,qcm2290.yaml | 4 $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 31 '^interconnect-[a-z0-9]+$': 34 The interconnect providers do not have a separate QoS register space, 62 snoc: interconnect@1880000 { 65 #interconnect-cells = <1>; 67 qup_virt: interconnect-qup { 69 #interconnect-cells = <1>; 72 mmnrt_virt: interconnect-mmnrt { [all …]
|
H A D | qcom,sm6115.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm6115.yaml# 7 title: Qualcomm SM6115 Network-On-Chip interconnect 13 The Qualcomm SM6115 interconnect providers support adjusting the 36 '^interconnect-[a-z0-9]+$': 39 The interconnect providers do not have a separate QoS register space, 119 snoc: interconnect@1880000 { 130 #interconnect-cells = <1>; 132 qup_virt: interconnect-clk { 134 #interconnect-cells = <1>; 137 mmnrt_virt: interconnect-mmnrt { [all …]
|
H A D | qcom,sm6350-rpmh.yaml | 4 $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 …]
|
H A D | qcom,msm8953.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8953.yaml# 7 title: Qualcomm MSM8953 Network-On-Chip interconnect 13 The Qualcomm MSM8953 interconnect providers support adjusting the 16 See also: include/dt-bindings/interconnect/qcom,msm8953.h 34 '#interconnect-cells': 38 '^interconnect-[a-z0-9\-]+$': 43 The interconnect providers do not have a separate QoS register space, 52 - '#interconnect-cells' 57 - '#interconnect-cells' 89 snoc: interconnect@580000 { [all …]
|
H A D | qcom,sm7150-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm7150-rpmh.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on SM7150 13 RPMh interconnect providers support system bandwidth requirements through 16 See also:: include/dt-bindings/interconnect/qcom,sm7150-rpmh.h 39 '^interconnect-[0-9]+$': 42 The interconnect providers do not have a separate QoS register space, 66 mc_virt: interconnect@1380000 { 69 #interconnect-cells = <2>; 73 system_noc: interconnect@1620000 { 76 #interconnect-cells = <2>; [all …]
|
H A D | qcom,qdu1000-rpmh.yaml | 4 $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>;
|
H A D | qcom,msm8939.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8939.yaml# 7 title: Qualcomm MSM8937/MSM8939/MSM8976 Network-On-Chip interconnect 13 The Qualcomm MSM8937/MSM8939/MSM8976 interconnect providers support 36 '^interconnect-[a-z0-9\-]+$': 40 The interconnect providers do not have a separate QoS register space, 68 snoc: interconnect@580000 { 71 #interconnect-cells = <1>; 73 snoc_mm: interconnect-snoc { 75 #interconnect-cells = <1>;
|
H A D | qcom,sc7280-rpmh.yaml | 4 $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 104 interconnect { 106 #interconnect-cells = <2>; 110 interconnect@9100000 { 113 #interconnect-cells = <2>; 117 interconnect@16e0000 { 120 #interconnect-cells = <2>;
|
H A D | qcom,sdx75-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sdx75-rpmh.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on SDX75 13 RPMh interconnect providers support system bandwidth requirements through 30 '#interconnect-cells': true 80 clk_virt: interconnect-0 { 82 #interconnect-cells = <2>; 87 system_noc: interconnect@1640000 { 90 #interconnect-cells = <2>;
|
H A D | qcom,msm8974.yaml | 4 $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>;
|
H A D | qcom,x1e80100-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,x1e80100-rpmh.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on X1E80100 14 RPMh interconnect providers support system bandwidth requirements through 21 See also:: include/dt-bindings/interconnect/qcom,x1e80100-rpmh.h 72 clk_virt: interconnect-0 { 74 #interconnect-cells = <2>; 78 aggre1_noc: interconnect@16e0000 { 81 #interconnect-cells = <2>;
|
H A D | qcom,sm8450-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm8450-rpmh.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on SM8450 14 RPMh interconnect providers support system bandwidth requirements through 17 See also:: include/dt-bindings/interconnect/qcom,sm8450.h 109 interconnect-0 { 111 #interconnect-cells = <2>; 115 interconnect@1700000 { 118 #interconnect-cells = <2>;
|
H A D | qcom,osm-l3.yaml | 4 $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 51 '#interconnect-cells': 59 - '#interconnect-cells' 69 osm_l3: interconnect@17d41000 { 76 #interconnect-cells = <1>;
|
/linux/drivers/interconnect/qcom/ |
H A D | Kconfig | 3 tristate "Qualcomm Network-on-Chip interconnect drivers" 6 Support for Qualcomm's Network-on-Chip interconnect hardware. 12 tristate "Qualcomm MSM8909 interconnect driver" 21 tristate "Qualcomm MSM8916 interconnect driver" 30 tristate "Qualcomm MSM8937 interconnect driver" 39 tristate "Qualcomm MSM8939 interconnect driver" 48 tristate "Qualcomm MSM8953 interconnect driver" 57 tristate "Qualcomm MSM8974 interconnect driver" 66 tristate "Qualcomm MSM8976 interconnect driver" 75 tristate "Qualcomm MSM8996 interconnect driver" [all …]
|
/linux/Documentation/driver-api/ |
H A D | interconnect.rst | 4 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 …]
|
/linux/drivers/interconnect/imx/ |
H A D | Makefile | 1 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
|
H A D | Kconfig | 2 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"
|
/linux/drivers/net/ipa/ |
H A D | ipa_power.c | 9 #include <linux/interconnect.h> 42 * @interconnect_count: Number of elements in interconnect[] 43 * @interconnect: Interconnect array 50 struct icc_bulk_data interconnect[] __counted_by(interconnect_count); 57 struct icc_bulk_data *interconnect; in ipa_interconnect_init() local 61 /* Initialize our interconnect data array for bulk operations */ in ipa_interconnect_init() 62 interconnect = &power->interconnect[0]; in ipa_interconnect_init() 64 /* interconnect->path is filled in by of_icc_bulk_get() */ in ipa_interconnect_init() 65 interconnect->name = data->name; in ipa_interconnect_init() 66 interconnect->avg_bw = data->average_bandwidth; in ipa_interconnect_init() [all …]
|
/linux/drivers/interconnect/ |
H A D | Kconfig | 2 menuconfig INTERCONNECT config 3 bool "On-Chip Interconnect management support" 12 if INTERCONNECT 14 source "drivers/interconnect/imx/Kconfig" 15 source "drivers/interconnect/mediatek/Kconfig" 16 source "drivers/interconnect/qcom/Kconfig" 17 source "drivers/interconnect/samsung/Kconfig" 23 Support for wrapping clocks into the interconnect nodes.
|
H A D | core.c | 3 * Interconnect framework core driver 13 #include <linux/interconnect.h> 14 #include <linux/interconnect-provider.h> 341 * @spec: OF phandle args to map into an interconnect node. 345 * interconnect providers that have one device tree node and provide 346 * multiple interconnect nodes. A single cell is used as an index into 366 * of_icc_get_from_provider() - Look-up interconnect node 369 * Looks for interconnect provider under the node specified by @spec and if 447 * @idx: interconnect path index 452 * If the interconnect API is disabled, NULL is returned and the consumer [all …]
|
/linux/Documentation/devicetree/bindings/bus/ |
H A D | ti-sysc.yaml | 7 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 …]
|
H A D | baikal,bt1-axi.yaml | 16 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>;
|
/linux/drivers/interconnect/mediatek/ |
H A D | Kconfig | 4 bool "MediaTek interconnect drivers" 7 Support for MediaTek's bus interconnect hardware. 10 tristate "MediaTek DVFSRC EMI interconnect driver" 14 interconnect on SoCs equipped with the integrated Dynamic 18 tristate "MediaTek MT8183 interconnect driver" 21 This is a driver for the MediaTek bus interconnect on MT8183-based 25 tristate "MediaTek MT8195 interconnect driver" 28 This is a driver for the MediaTek bus interconnect on MT8195-based
|
/linux/include/linux/ |
H A D | interconnect-provider.h | 10 #include <linux/interconnect.h> 29 * struct icc_onecell_data - driver data for onecell interconnect providers 43 * struct icc_provider - interconnect provider (controller) entity that might 44 * provide multiple interconnect controls 46 * @provider_list: list of the registered interconnect providers 47 * @nodes: internal list of the interconnect provider nodes 55 * @dev: the device this interconnect provider belongs to 78 * struct icc_node - entity that is part of the interconnect topology 83 * @num_links: number of links to other interconnect nodes 84 * @provider: points to the interconnect provider of this node
|