From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus WALLEIJ <linus.walleij@stericsson.com>
Cc: Sundar R IYER <sundar.iyer@stericsson.com>,
Deepak Sikri <deepak.sikri79@gmail.com>,
Viresh KUMAR <viresh.kumar@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vipin KUMAR <vipin.kumar@st.com>,
Shiraz HASHIM <shiraz.hashim@st.com>,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>
Subject: RE: [linux-pm] Power Domain Framework
Date: Mon, 17 May 2010 15:17:16 -0700 [thread overview]
Message-ID: <1274134636.2698.170.camel@finisterre.wolfsonmicro.main> (raw)
In-Reply-To: <CEE6BB42CAD6E947908279175AF8470A025A72624A@EXDCVYMBSTM006.EQ1STM.local> (sfid-20100517_224652_794912_8E56D9D6)
On Mon, 2010-05-17 at 23:46 +0200, Linus WALLEIJ wrote:
> [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.
Yeah, sure - obviously, the generic concept of power domains is
something that does exist within the off-SoC hardware, but on-SoC the
end implementation is a bit different.
next prev parent reply other threads:[~2010-05-17 22:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinZU1D1rMOBQDi47tRhXrOXwduQIdni7bCXdce0@mail.gmail.com>
2010-05-10 14:05 ` Mark Brown
2010-05-16 11:13 ` Sundar
2010-05-17 3:16 ` Mark Brown
[not found] ` <AANLkTimDdBCnRFMDiUkuNKanOzuPNwCpfRv9Gsi03Lsy@mail.gmail.com>
2010-05-17 13:33 ` Fwd: " Sundar
2010-05-17 14:33 ` Mark Brown
2010-05-17 16:23 ` Sundar
2010-05-17 16:35 ` Sundar R Iyer
2010-05-17 17:04 ` Mark Brown
2010-05-17 17:45 ` Sundar R Iyer
2010-05-17 20:38 ` Linus WALLEIJ
2010-05-17 21:18 ` Mark Brown
2010-05-17 21:46 ` Linus WALLEIJ
2010-05-17 22:17 ` Mark Brown [this message]
2010-05-18 6:00 ` Sundar R Iyer
[not found] ` <AANLkTinTdTp_X4lGtZ0hCaVJN5GmvI0tXR1RTRkRNkjN@mail.gmail.com>
2010-05-24 3:39 ` Mark Brown
2010-05-26 8:33 ` Sundar R IYER
2010-05-26 21:07 ` Mark Brown
2010-05-27 3:01 ` Paul Mundt
2010-05-27 6:51 ` Mark Brown
2010-05-17 20:20 ` Fwd: " Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1274134636.2698.170.camel@finisterre.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=armando.visconti@st.com \
--cc=deepak.sikri79@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rajeev-dlh.kumar@st.com \
--cc=shiraz.hashim@st.com \
--cc=sundar.iyer@stericsson.com \
--cc=vipin.kumar@st.com \
--cc=viresh.kumar@st.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®