| /linux-6.3-rc2/Documentation/devicetree/bindings/interconnect/ |
| A D | interconnect.txt | 8 = interconnect providers =
10 The interconnect provider binding is intended to represent the interconnect
12 nodes, which expose the interconnect related capabilities of the interconnect
21 - #interconnect-cells : number of cells in a interconnect specifier needed to
27 snoc: interconnect@580000 {
29 #interconnect-cells = <1>;
37 = interconnect consumers =
54 interconnect-names : List of interconnect path name strings sorted in the same
56 interconnect-names to match interconnect paths with interconnect
75 interconnect-cells = <2>;
[all …]
|
| A D | qcom,qcm2290.yaml | 26 '#interconnect-cells':
41 '^interconnect-[a-z0-9]+$':
54 '#interconnect-cells':
69 - '#interconnect-cells'
78 - '#interconnect-cells'
88 snoc: interconnect@1880000 {
91 #interconnect-cells = <1>;
121 cnoc: interconnect@1900000 {
124 #interconnect-cells = <1>;
130 bimc: interconnect@4480000 {
[all …]
|
| A D | qcom,sm6350-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm6350-rpmh.yaml#
13 Qualcomm RPMh-based interconnect provider on SM6350.
33 '#interconnect-cells': true
36 '^interconnect-[a-z0-9\-]+$':
49 '#interconnect-cells': true
64 config_noc: interconnect@1500000 {
67 #interconnect-cells = <2>;
71 system_noc: interconnect@1620000 {
74 #interconnect-cells = <2>;
77 clk_virt: interconnect-clk-virt {
[all …]
|
| A D | qcom,rpm.yaml | 47 '#interconnect-cells':
50 interconnect node id, <2> requires the interconnect node id and an
67 '^interconnect-[a-z0-9]+$':
77 '#interconnect-cells':
92 - '#interconnect-cells'
99 - '#interconnect-cells'
255 bimc: interconnect@400000 {
258 #interconnect-cells = <1>;
264 pcnoc: interconnect@500000 {
267 #interconnect-cells = <1>;
[all …]
|
| A D | qcom,qdu1000-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,qdu1000-rpmh.yaml#
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>;
|
| A D | qcom,sc7280-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sc7280-rpmh.yaml#
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>;
|
| A D | qcom,msm8974.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8974.yaml#
13 The Qualcomm MSM8974 interconnect providers support setting system
29 '#interconnect-cells':
45 - '#interconnect-cells'
55 bimc: interconnect@fc380000 {
58 #interconnect-cells = <1>;
|
| A D | qcom,osm-l3.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,osm-l3.yaml#
14 The OSM L3 interconnect provider aggregates the L3 bandwidth requests
49 '#interconnect-cells':
57 - '#interconnect-cells'
67 osm_l3: interconnect@17d41000 {
74 #interconnect-cells = <1>;
|
| A D | fsl,imx8m-noc.yaml | 4 $id: http://devicetree.org/schemas/interconnect/fsl,imx8m-noc.yaml#
22 interconnect IPs into imx SOCs.
58 '#interconnect-cells':
60 If specified then also act as an interconnect provider. Should only be
73 #include <dt-bindings/interconnect/imx8mm.h>
76 noc: interconnect@32700000 {
80 #interconnect-cells = <1>;
|
| A D | qcom,sm8450-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm8450-rpmh.yaml#
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>;
|
| A D | qcom,sc8280xp-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sc8280xp-rpmh.yaml#
14 RPMh interconnect providers support system bandwidth requirements through
17 See also:: include/dt-bindings/interconnect/qcom,sc8280xp.h
45 interconnect-0 {
47 #interconnect-cells = <2>;
|
| A D | qcom,rpmh-common.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,rpmh-common.yaml#
14 RPMh interconnect providers support system bandwidth requirements through
22 '#interconnect-cells':
32 this interconnect to send RPMh commands.
40 - '#interconnect-cells'
|
| A D | qcom,sa8775p-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sa8775p-rpmh.yaml#
13 RPMh interconnect providers support system bandwidth requirements through
16 See also:: include/dt-bindings/interconnect/qcom,sa8775p.h
46 aggre1_noc: interconnect-aggre1-noc {
48 #interconnect-cells = <2>;
|
| A D | qcom,sm8550-rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm8550-rpmh.yaml#
14 RPMh interconnect providers support system bandwidth requirements through
21 See also:: include/dt-bindings/interconnect/qcom,sm8550-rpmh.h
126 clk_virt: interconnect-0 {
128 #interconnect-cells = <2>;
132 aggre1_noc: interconnect@16e0000 {
135 #interconnect-cells = <2>;
|
| A D | qcom,rpmh.yaml | 4 $id: http://devicetree.org/schemas/interconnect/qcom,rpmh.yaml#
14 RPMh interconnect providers support system bandwidth requirements through
106 '#interconnect-cells': true
116 #include <dt-bindings/interconnect/qcom,sdm845.h>
118 mem_noc: interconnect@1380000 {
121 #interconnect-cells = <1>;
125 mmss_noc: interconnect@1740000 {
128 #interconnect-cells = <1>;
|
| /linux-6.3-rc2/drivers/interconnect/imx/ |
| 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
|
| 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-6.3-rc2/Documentation/driver-api/ |
| A D | interconnect.rst | 18 An example of interconnect buses are the interconnects between various
60 port. Each interconnect provider consists of multiple interconnect nodes,
63 called an interconnect node, which belongs to the Mem NoC interconnect provider.
82 configure interconnect bus hardware. The interconnect provider drivers should
83 be registered with the interconnect provider core.
85 .. kernel-doc:: include/linux/interconnect-provider.h
92 for these interconnect paths. These interfaces are not currently
102 ``/sys/kernel/debug/interconnect/interconnect_summary``:
107 ``/sys/kernel/debug/interconnect/interconnect_graph``:
109 Show the interconnect graph in the graphviz dot format. It shows all
[all …]
|
| /linux-6.3-rc2/drivers/interconnect/qcom/ |
| A D | Kconfig | 3 tristate "Qualcomm Network-on-Chip interconnect drivers"
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"
55 tristate "Qualcomm QCM2290 interconnect driver"
64 tristate "Qualcomm QCS404 interconnect driver"
105 tristate "Qualcomm SC7180 interconnect driver"
168 tristate "Qualcomm SDX55 interconnect driver"
[all …]
|
| /linux-6.3-rc2/drivers/net/ipa/ |
| A D | ipa_power.c | 70 struct icc_bulk_data interconnect[]; member
77 struct icc_bulk_data *interconnect; in ipa_interconnect_init() local
82 interconnect = &power->interconnect[0]; in ipa_interconnect_init()
85 interconnect->name = data->name; in ipa_interconnect_init()
86 interconnect->avg_bw = data->average_bandwidth; in ipa_interconnect_init()
87 interconnect->peak_bw = data->peak_bandwidth; in ipa_interconnect_init()
89 interconnect++; in ipa_interconnect_init()
93 power->interconnect); in ipa_interconnect_init()
103 icc_bulk_put(power->interconnect_count, power->interconnect); in ipa_interconnect_init()
111 icc_bulk_put(power->interconnect_count, power->interconnect); in ipa_interconnect_exit()
[all …]
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/soc/imx/ |
| A D | fsl,imx8mm-vpu-blk-ctrl.yaml | 44 interconnect-names:
91 - description: G1 decoder interconnect
92 - description: G2 decoder interconnect
95 interconnect-names:
136 - description: G1 decoder interconnect
137 - description: G2 decoder interconnect
138 - description: VC8000E encoder interconnect
140 interconnect-names:
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/devfreq/ |
| A D | nvidia,tegra30-actmon.yaml | 53 interconnect-names:
57 Should include name of the interconnect path for each interconnect
78 - interconnect-names
98 #interconnect-cells = <1>;
111 #interconnect-cells = <0>;
124 interconnect-names = "cpu-read";
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/arm/sunxi/ |
| A D | allwinner,sun4i-a10-mbus.yaml | 20 the interconnects and interconnect-names properties set to the MBUS
21 controller and with "dma-mem" as the interconnect name.
24 "#interconnect-cells":
50 - description: MBUS interconnect/bandwidth limit/PMU registers
62 - description: MBUS interconnect module clock
87 - "#interconnect-cells"
148 #interconnect-cells = <1>;
165 #interconnect-cells = <1>;
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/clock/ |
| A D | qcom,msm8996-cbf.yaml | 14 interconnect between two CPU clusters.
31 '#interconnect-cells':
39 - '#interconnect-cells'
51 #interconnect-cells = <1>;
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/bus/ |
| 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,
|