From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754298AbaCLNeg (ORCPT ); Wed, 12 Mar 2014 09:34:36 -0400 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:44089 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754137AbaCLNee (ORCPT ); Wed, 12 Mar 2014 09:34:34 -0400 Date: Wed, 12 Mar 2014 13:33:39 +0000 From: Mark Rutland To: Matt Porter Cc: Rob Herring , Pawel Moll , Ian Campbell , Kumar Gala , Samuel Ortiz , Lee Jones , Liam Girdwood , Mark Brown , Christian Daudt , Devicetree List , Linux ARM Kernel List , Linux Kernel Mailing List Subject: Re: [PATCH v4 1/5] mfd: add bcm590xx pmu DT binding Message-ID: <20140312133339.GC17461@e106331-lin.cambridge.arm.com> References: <1394580837-8331-1-git-send-email-mporter@linaro.org> <1394580837-8331-2-git-send-email-mporter@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1394580837-8331-2-git-send-email-mporter@linaro.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 11, 2014 at 11:33:53PM +0000, Matt Porter wrote: > Add a DT binding for the BCM590xx PMUs. The binding inherits from > the generic regulator bindings. > > Signed-off-by: Matt Porter > Reviewed-by: Tim Kryger > Reviewed-by: Markus Mayer > --- > Documentation/devicetree/bindings/mfd/bcm590xx.txt | 41 ++++++++++++++++++++++ > 1 file changed, 41 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/bcm590xx.txt > > diff --git a/Documentation/devicetree/bindings/mfd/bcm590xx.txt b/Documentation/devicetree/bindings/mfd/bcm590xx.txt > new file mode 100644 > index 0000000..2300246 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/bcm590xx.txt > @@ -0,0 +1,41 @@ > +------------------------------- > +BCM590xx Power Management Units > +------------------------------- > + > +Required properties: > +- compatible: "brcm,bcm59056" > +- reg: I2C slave address > +- interrupts: interrupt for the PMU. Generic interrupt client node bindings > + are described in interrupt-controller/interrupts.txt This all looks sane. > + > +------------------ > +Voltage Regulators > +------------------ > + > +Optional properties: > +- regulators: This is the list of child nodes that specify the regulator > + initialization data for defined regulators. Generic regulator bindings > + are described in regulator/regulator.txt. This is a subnode, not a property. How about: Optional child nodes: - regulators: container node for regulators follwoing the generic regulator binding in regulator/regulator.txt. > + > + The valid regulator nodes for BCM59056 are: s/nodes/node names/ > + rfldo, camldo1, camldo2, simldo1, simldo2, sdldo, sdxldo, > + mmcldo1, mmcldo2, audldo, micldo, usbldo, vibldo, > + csr, iosr1, iosr2, msr, sdsr1, sdsr2, vsr > + > +Example: > + pmu: bcm59056@8 { > + compatible = "brcm,bcm59056"; > + reg = <0x08>; > + interrupts = ; > + regulators { > + #address-cells = <1>; > + #size-cells = <0>; > + > + rfldo_reg: rfldo { > + regulator-min-microvolt = <1200000>; > + regulator-max-microvolt = <3300000>; Are any specific properties required on these children? Thanks, Mark. > + }; > + > + ... > + }; > + }; > -- > 1.8.4 > >