| Message ID | 20180309210958.16672-7-georgi.djakov@linaro.org (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Fri 09 Mar 13:09 PST 2018, Georgi Djakov wrote: > Add documentation for the interconnect consumer bindings, that will allow > to link a device node (consumer) to its interconnect controller hardware. > > Tha aim is to enable drivers to request a framework API to configure an > interconnect path by providing their struct device pointer and a name. > > Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org> > --- > .../bindings/interconnect/interconnect.txt | 23 ++++++++++++++++++++++ > 1 file changed, 23 insertions(+) > > diff --git a/Documentation/devicetree/bindings/interconnect/interconnect.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt > index 70612bb201e4..7935abf10c4b 100644 > --- a/Documentation/devicetree/bindings/interconnect/interconnect.txt > +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt > @@ -45,3 +45,26 @@ Examples: > status = "okay"; > }; > > += interconnect consumers = > + > +The interconnect consumers are device nodes which consume the interconnect > +path(s) provided by the interconnect provider. There can be multiple > +interconnect providers on a SoC and the consumer may consume multiple paths > +from different providers depending on usecase and the components it has to > +interact with. > + > +Required-properties: > +interconnects: Pairs of phandles and interconnect provider specifier to denote > + the source and the destination port of the interconnect path. > +interconnect-names: List of interconnect path name strings sorted in the same > + order as the interconnects property. Consumers drivers will use > + interconnect-names to match interconnect paths with interconnect > + specifiers. Analog to other subsystems the -names property should be optional, at least when there's only a single entry in interconnects. > + > +Example: > + > + sdhci@7864000 { > + ... > + interconnects = <&pnoc 78 &bimc 512> > + interconnect-names = "memory"; > + }; Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Bjorn, On 03/19/2018 06:49 AM, Bjorn Andersson wrote: > On Fri 09 Mar 13:09 PST 2018, Georgi Djakov wrote: > >> Add documentation for the interconnect consumer bindings, that will allow >> to link a device node (consumer) to its interconnect controller hardware. >> >> Tha aim is to enable drivers to request a framework API to configure an >> interconnect path by providing their struct device pointer and a name. >> >> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org> >> --- >> .../bindings/interconnect/interconnect.txt | 23 ++++++++++++++++++++++ >> 1 file changed, 23 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/interconnect/interconnect.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt >> index 70612bb201e4..7935abf10c4b 100644 >> --- a/Documentation/devicetree/bindings/interconnect/interconnect.txt >> +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt >> @@ -45,3 +45,26 @@ Examples: >> status = "okay"; >> }; >> >> += interconnect consumers = >> + >> +The interconnect consumers are device nodes which consume the interconnect >> +path(s) provided by the interconnect provider. There can be multiple >> +interconnect providers on a SoC and the consumer may consume multiple paths >> +from different providers depending on usecase and the components it has to >> +interact with. >> + >> +Required-properties: >> +interconnects: Pairs of phandles and interconnect provider specifier to denote >> + the source and the destination port of the interconnect path. >> +interconnect-names: List of interconnect path name strings sorted in the same >> + order as the interconnects property. Consumers drivers will use >> + interconnect-names to match interconnect paths with interconnect >> + specifiers. > > Analog to other subsystems the -names property should be optional, at > least when there's only a single entry in interconnects. > Will do it. Thanks, Georgi -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/interconnect/interconnect.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt index 70612bb201e4..7935abf10c4b 100644 --- a/Documentation/devicetree/bindings/interconnect/interconnect.txt +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt @@ -45,3 +45,26 @@ Examples: status = "okay"; }; += interconnect consumers = + +The interconnect consumers are device nodes which consume the interconnect +path(s) provided by the interconnect provider. There can be multiple +interconnect providers on a SoC and the consumer may consume multiple paths +from different providers depending on usecase and the components it has to +interact with. + +Required-properties: +interconnects: Pairs of phandles and interconnect provider specifier to denote + the source and the destination port of the interconnect path. +interconnect-names: List of interconnect path name strings sorted in the same + order as the interconnects property. Consumers drivers will use + interconnect-names to match interconnect paths with interconnect + specifiers. + +Example: + + sdhci@7864000 { + ... + interconnects = <&pnoc 78 &bimc 512> + interconnect-names = "memory"; + };
Add documentation for the interconnect consumer bindings, that will allow to link a device node (consumer) to its interconnect controller hardware. Tha aim is to enable drivers to request a framework API to configure an interconnect path by providing their struct device pointer and a name. Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org> --- .../bindings/interconnect/interconnect.txt | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html