[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FCDDFFC.3000902@linaro.org>
Date: Tue, 05 Jun 2012 11:31:24 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
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 01/06/12 09:48, Mark Brown wrote:
> 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.
I mean they both link regulator<->consumer and apply the name "vmmc" to
the supply, or am I missing something / getting confused?
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
M: +44 77 88 633 515
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists