Re: [PATCH RESEND] ARM: tegra: set regulator full constraints

From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org"
	<swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RESEND] ARM: tegra: set regulator full constraints
Date: Wed, 6 Nov 2013 08:51:00 +0000	[thread overview]
Message-ID: <20131106085100.GB11602@sirena.org.uk> (raw)
In-Reply-To: <5278B4CB.9050305-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

On Tue, Nov 05, 2013 at 05:05:15PM +0800, Wei Ni wrote:
> On 11/05/2013 12:18 AM, Mark Brown wrote:

> > We can do it as part of parsing the DT or deciding to parse the DT.

> I checked the kernel codes, it seems the different arch uses different
> way to parse DT, and I think these codes are related with DT, it's not
> better to add such regulator full constraints codes.

There's a lot of shared code there, and it's most likely that any new
platforms will be using the flattened device tree code.  Anything other
than doing this when we start device tree is going to leave a window
where we will be using device tree but not handling that in the
regulator API.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]