Date: Sat, 10 Jan 2009 18:58:31 +0000
From: Mark Brown <broonie@sirena.org.uk>
To: Jonathan Cameron <Jonathan.Cameron@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Liam Girdwood <lrg@kernel.org>
Message-ID: <20090110185830.GC31525@sirena.org.uk>
References: <4968BE74.1070903@gmail.com> <20090110174602.GA31525@sirena.org.uk> <4968E365.5040409@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4968E365.5040409@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: Regulator: Use case query (many devices need to reg their
	voltage requirements?)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1220
Lines: 28

On Sat, Jan 10, 2009 at 06:05:25PM +0000, Jonathan Cameron wrote:

> It maps fine, particularly as quite a few daughter boards have local (be
> it static)
> regulators to ensure clean supplies etc.

Note that there's a fixed voltage regulator driver in the tree for
handling those.

> >   There will also be issues if the drivers are for chips
> > which have multiple software compatible variants with differing power
> > requirements.

> Yup, though in many cases they have different part numbers etc and can
> be handled via multiple
> driver registrations or alias provisions such as in i2c.  This is how
> things like adc's with differing
> numbers of inputs depending on precise model are handled anyway.

That is doable but error prone, especially if doing something like
adding regulator support to an existing driver or when new parts come
out.  Often the part numbers are only slight different (adding an
additional letter at the end of the day) which doesn't help.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/