[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120601084850.GJ24139@opensource.wolfsonmicro.com>
Date: Fri, 1 Jun 2012 09:48:51 +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 Fri, Jun 01, 2012 at 12:36:28PM +0800, Lee Jones wrote:
> This:
> >sdi@...26000 {
> > vmmc-supply = <&ab8500_ldo_aux3_reg>;
> >};
> Is the same as, and will cause no more issues than:
> >static struct regulator_consumer_supply ab8500_vaux3_consumers[] = {
> > REGULATOR_SUPPLY("vmmc", "sdi0"),
> >};
> ... because only nodes which we care about (dictated by compatible
> declaration protections) will be parsed. So different platforms will
> not affect each other.
What makes you say the two are equivalent? The former is a reference
from a consumer device to a named regulator while the latter is a
reference from a regulator to a named consumer.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists