On Wed, Oct 10, 2018 at 02:54:34PM +0530, Sravanthi Kollukuduru wrote: > Add interconnect properties such as interconnect provider specifier > , the edge source and destination ports which are required by the > interconnect API to configure interconnect path for MDSS. > > Changes in v2: > -none > > Signed-off-by: Sravanthi Kollukuduru <skolluku@xxxxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/display/msm/dpu.txt | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/msm/dpu.txt b/Documentation/devicetree/bindings/display/msm/dpu.txt > index ad2e8830324e..abd4d99b5030 100644 > --- a/Documentation/devicetree/bindings/display/msm/dpu.txt > +++ b/Documentation/devicetree/bindings/display/msm/dpu.txt > @@ -28,6 +28,11 @@ Required properties: > - #address-cells: number of address cells for the MDSS children. Should be 1. > - #size-cells: Should be 1. > - ranges: parent bus address space is the same as the child bus address space. > +- interconnects : pairs of phandles and interconnect provider specifier to > + denote the edge source and destination ports 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. Don't need to define common properties. Just list their constraints such as how many. > > Optional properties: > - assigned-clocks: list of clock specifiers for clocks needing rate assignment > @@ -86,6 +91,9 @@ Example: > interrupt-controller; > #interrupt-cells = <1>; > > + interconnects = <&qnoc 38 &qnoc 512>; > + interconnect-names = "port0"; -names is kind of pointless here. IMO, interconnect-names should describe the path. > + > iommus = <&apps_iommu 0>; > > #address-cells = <2>; > -- > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, > a Linux Foundation Collaborative Project >
