From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sundar <sunder.svit@gmail.com>
Cc: Viresh KUMAR <viresh.kumar@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
Linus WALLEIJ <linus.walleij@stericsson.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>,
STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] Power Domain Framework
Date: Sun, 23 May 2010 20:39:00 -0700 [thread overview]
Message-ID: <20100524033859.GB24480@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTinTdTp_X4lGtZ0hCaVJN5GmvI0tXR1RTRkRNkjN@mail.gmail.com>
On Sat, May 22, 2010 at 09:32:10AM +0530, Sundar wrote:
> > operating mode for the entire power domain. For example, I can see
> > hardware requiring that if more than a given number of blocks are
> > enabled at any level a higher operating point is selected.
> To me, since such a requirement is a constraint on the regulator,
> this can be added as a flag to the regulator details.
> This flag can then be used in the set_opp* functions to check the
> condition along with the client dependencies!
This is just one example of something that might come up and need
fitting in to the regulator API which is substantially different to the
needs of the core regulator applications. As I keep saying I'm just not
seeing much more overlap here with the regulator API than I do with the
clock API: it feels like you've got another use case which needs an API
with a similar structure and the reference counted enable and disable
calls but otherwise very little overlap.
I don't think the enable and disable calls are enough of an overlap to
mean that the regulator use case and the operating point use case are
going to overlap well, it feels like it'd cause pain trying to match the
concepts between the two APIs.
next prev parent reply other threads:[~2010-05-24 3:38 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 ` [linux-pm] Power Domain Framework 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
2010-05-18 6:00 ` Sundar R Iyer
[not found] ` <AANLkTinTdTp_X4lGtZ0hCaVJN5GmvI0tXR1RTRkRNkjN@mail.gmail.com>
2010-05-24 3:39 ` Mark Brown [this message]
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=20100524033859.GB24480@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=armando.visconti@st.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=sunder.svit@gmail.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;
as well as URLs for NNTP newsgroup(s).