Thread (19 messages) 19 messages, 3 authors, 2011-03-30

[PATCH v2 2/2] regulator: Propagate uA_load requirements up supply chain

From: Mark Brown <hidden>
Date: 2011-03-30 01:00:14
Also in: linux-arm-msm, lkml

On Wed, Mar 30, 2011 at 06:20:10AM +0900, Mark Brown wrote:
On Tue, Mar 29, 2011 at 09:08:15AM -0700, David Collins wrote:
quoted
I agree that it would be beneficial to change regulator_dev.supply from
type struct regulator_dev * to type struct regulator *.  However, I think
that going that route will be a major undertaking with a lot of details to
Hrm, it doesn't look too bad - as far as I can see it should just be
fairly direct refactorings of each of get, put, enable and disable?
I had a look at this, it all looks very straightforward apart from get
where we need to either do a dance to set up a supply mapping or
restructure to expose the core get operation internally without map
lookups (the latter I think) and that doesn't seem terribly invasive.
I may actually try coding it up next time I'm sitting in front of an
appropriate test system.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help