[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140311154930.GJ25092@beef>
Date: Tue, 11 Mar 2014 11:49:30 -0400
From: Matt Porter <mporter@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Christian Daudt <bcm@...thebug.org>,
Devicetree List <devicetree@...r.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/5] mfd: add bcm590xx pmu DT binding
On Wed, Feb 19, 2014 at 01:47:26PM +0900, Mark Brown wrote:
> On Tue, Feb 18, 2014 at 06:17:08PM -0500, Matt Porter wrote:
>
> > +
> > + rfldo_reg: regulator@0 {
> > + reg = <0>;
>
> What do these reg values mean, they don't seem to be documented in the
> binding?
Dropped this and the deprecated regulator-compatible property in v3 in
favor of using node name matching.
-Matt
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists