[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120530164152.GP9947@opensource.wolfsonmicro.com>
Date: Wed, 30 May 2012 17:41:52 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: Chris Ball <cjb@...top.org>,
Linus Walleij <linus.walleij@...ricsson.com>,
Bengt Jonsson <bengt.g.jonsson@...ricsson.com>,
Mattias WALLIN <mattias.wallin@...ricsson.com>,
linux-arm-kernel@...ts.infradead.org, sameo@...ux.intel.com,
grant.likely@...retlab.ca, linux-kernel@...r.kernel.org,
arnd@...db.de, Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH 08/22] regulator: Change ab8500 match names to reflect
Device Tree
On Wed, May 30, 2012 at 11:22:33PM +0800, Lee Jones wrote:
> On 30/05/12 23:11, Mark Brown wrote:
> >> vin-supply =<&db8500_vape_reg>;
> >> vmmc-supply =<&ab8500_ldo_aux2_reg>;
> >Oh, oops. This is going to be fun when someone puts down two of the
> >same PMIC on a system...
> What does that mean sorry?
Lots of regulators are using this mechanism for identifying child nodes.
If the node name is also used as a handle by other things to reference
the regulator then if you have two PMICs of the same type DTC isn't
going to be able to figure out which node you mean.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists