Hi Rob, > -----Original Message----- > From: Rob Herring [mailto:[email protected]] > Sent: Tuesday, September 25, 2018 9:15 AM > To: Jolly Shah <[email protected]> > Cc: Matthias Brugger <[email protected]>; Andy Gross > <[email protected]>; Shawn Guo <[email protected]>; Geert > Uytterhoeven <[email protected]>; Bjorn Andersson > <[email protected]>; Sean Wang <[email protected]>; > Marek Szyprowski <[email protected]>; Michal Simek > <[email protected]>; Mark Rutland <[email protected]>; Rajan Vaja > <[email protected]>; [email protected]; moderated > list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE <linux-arm- > [email protected]>; [email protected] > Subject: Re: [PATCH v2 1/3] dt-bindings: power: Add ZynqMP power domain > bindings > > On Thu, Sep 13, 2018 at 12:51 PM Jolly Shah <[email protected]> wrote: > > > > Hi Rob, > > > > > -----Original Message----- > > > From: Rob Herring [mailto:[email protected]] > > > Sent: Monday, August 20, 2018 12:46 PM > > > To: Jolly Shah <[email protected]> > > > Cc: [email protected]; [email protected]; > > > [email protected]; > > > [email protected]; [email protected]; > > > [email protected]; [email protected]; Michal Simek > > > <[email protected]>; [email protected]; Rajan Vaja > > > <[email protected]>; [email protected]; linux-arm- > > > [email protected]; [email protected]; Rajan Vaja > > > <[email protected]>; Jolly Shah <[email protected]> > > > Subject: Re: [PATCH v2 1/3] dt-bindings: power: Add ZynqMP power > > > domain bindings > > > > > > On Thu, Aug 16, 2018 at 12:21:42PM -0700, Jolly Shah wrote: > > > > From: Rajan Vaja <[email protected]> > > > > > > > > Add documentation to describe ZynqMP power domain bindings. > > > > > > > > Signed-off-by: Rajan Vaja <[email protected]> > > > > Signed-off-by: Jolly Shah <[email protected]> > > > > --- > > > > .../firmware/xilinx/xlnx,zynqmp-firmware.txt | 47 > > > ++++++++++++++++++++++ > > > > > > This should be with all the other power domain bindings. > > > > > > > 1 file changed, 47 insertions(+) > > > > > > > > diff --git > > > > a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-fi > > > > rmwa > > > > re.txt > > > > b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-fi > > > > rmwa > > > > re.txt > > > > index d215d15..5fa10a0 100644 > > > > --- > > > > a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-fi > > > > rmwa > > > > re.txt > > > > +++ b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqm > > > > +++ p-fi > > > > +++ rmware.txt > > > > @@ -64,6 +64,29 @@ Output clocks are registered based on clock > > > > information received from firmware. Output clocks indexes are > > > > mentioned in include/dt-bindings/clock/xlnx,zynqmp-clk.h. > > > > > > > > +----------------------------------------------------------- > > > > +Device Tree Bindings for the Xilinx Zynq MPSoC PM domains > > > > +----------------------------------------------------------- > > > > +The binding for zynqmp-power-controller follow the common generic > > > > +PM domain binding[1]. > > > > + > > > > +[1] Documentation/devicetree/bindings/power/power_domain.txt > > > > + > > > > +== Zynq MPSoC Generic PM Domain Node == > > > > + > > > > +Required properties: > > > > + - compatible: Must be: "xlnx,zynqmp-power-controller" > > > > + > > > > +This node contains a number of subnodes, each representing a > > > > +single PM domain that PM domain consumer devices reference. > > > > + > > > > +== PM Domain Nodes == > > > > + > > > > +Required properties: > > > > + - #power-domain-cells: Number of cells in a PM domain specifier. > > > > Must > > > be 0. > > > > + - pd-id: Domain identifier as defined by platform firmware. > > > > + This identifier is passed to the PM firmware. > > > > > > Make this a cell for the power domain consumer. > > [Jolly] We have more than one Ids for GPU device. Also they don't have > > parent child relationship and hence are defined as flat hierarchy. > > (shown in example below) > > Then the gpu node should have: > > power-domains = <&pd 58 &pd 20 &pd 21>; > > Also, for this and the firmware reset binding, there is no reason that I see > to > make these all subnodes. A single firmware node can be a provider of multiple > functions. You only need child nodes if the sub-functions have their own > resources (clks, irqs, etc.). IOW, don't create nodes just because you want to > instantiate drivers that way. DT is not the only way to instantiate devices > for > drivers. >
Got it. Pushed v3 with suggested changes. Please review. > Rob
