mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sundar R Iyer <sundar.iyer@stericsson.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Linus WALLEIJ <linus.walleij@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: Tue, 18 May 2010 11:30:50 +0530	[thread overview]
Message-ID: <1274162450.17303.35.camel@bnru01> (raw)
In-Reply-To: <1274134636.2698.170.camel@finisterre.wolfsonmicro.main>

Hi,

> 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.

Exactly. This is what I can see if we can bridge this "a bit different".

True, I am dumb to miss out some points, but I think with more inputs,
more thinking, we can definitely make it generic!

Thinking out loud ( excuse me if this is dumb), At the end of the day,
how I see this benefiting a lay driver developer is : use the regulator
API for the appropriate power sources - your SoC domain, your external
regulator domain..etc..etc and ensure a very efficient (probably) run
time PM for your device. All that the Platform guy will do is iterate 
a list of domains on the platform, provide hookups, ensure constraints 
etc and the job is done. Even if the same IP is used on a different SoC,
you still ensure efficient savings in your driver itself.

> As I said in reply to the patch I am concerned that this may be an
> oversimplification relative to what general hardware needs.
Ohh. for the patch set, as I said, its only a primitive implementation.
With your inputs, we can definitely make it more efficient!

Regards,
Sundar


  reply	other threads:[~2010-05-18  6:01 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
2010-05-18  6:00                             ` Sundar R Iyer [this message]
     [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=1274162450.17303.35.camel@bnru01 \
    --to=sundar.iyer@stericsson.com \
    --cc=STEricsson_nomadik_linux@list.st.com \
    --cc=armando.visconti@st.com \
    --cc=broonie@opensource.wolfsonmicro.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=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

Powered by JetHome