[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CEE6BB42CAD6E947908279175AF8470A025A72624A@EXDCVYMBSTM006.EQ1STM.local>
Date: Mon, 17 May 2010 23:46:38 +0200
From: Linus WALLEIJ <linus.walleij@...ricsson.com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Sundar R IYER <sundar.iyer@...ricsson.com>,
Deepak Sikri <deepak.sikri79@...il.com>,
Viresh KUMAR <viresh.kumar@...com>,
Rajeev KUMAR <rajeev-dlh.kumar@...com>,
Armando VISCONTI <armando.visconti@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vipin KUMAR <vipin.kumar@...com>,
Shiraz HASHIM <shiraz.hashim@...com>,
"linux-pm@...ts.linux-foundation.org"
<linux-pm@...ts.linux-foundation.org>,
STEricsson_nomadik_linux <STEricsson_nomadik_linux@...t.st.com>
Subject: RE: [linux-pm] Power Domain Framework
[Mark]
> I do agree that separating out the common bits of power
> domain implementation would be good, my concerns here are around the
> level of integration with the regulator API.
The plenty talk about power domains in
Documentation/power/regulators/overview.txt
was what got us started in this regulator direction from the
beginning.
Anyhow: it will certainly be closely related even if we come
up with some different API for power domains so we're in the
right forum.
Linus
Powered by blists - more mailing lists