From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Bill Gatliff <bgat@billgatliff.com>,
Wolfram Sang <w.sang@pengutronix.de>,
Ben Dooks <ben-linux@fluff.org>,
linux-samsung-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH] i2c-s3c2410: Add stub runtime power management
Date: Mon, 23 Jan 2012 21:19:31 +0100 [thread overview]
Message-ID: <4F1DC0D3.4070408@gmail.com> (raw)
In-Reply-To: <20120122213952.GA29022@opensource.wolfsonmicro.com>
On 01/22/2012 10:39 PM, Mark Brown wrote:
> On Sun, Jan 22, 2012 at 06:48:36PM +0100, Sylwester Nawrocki wrote:
>> On 01/22/2012 06:27 PM, Bill Gatliff wrote:
>
>>> I for one would rather see in-kernel drivers that require it, and then
>
>> In fact we have to deal with the opposite now, as some existing drivers
>> have been used for multiple generations of SoC, where almost unchanged
>> device IPs are deployed. Those drivers were originally written for the
>> simplest SoCs.
>
> TBH I think most of the devices for which people are running these days
> will be able to get some win from the system wide stuff - the WFI modes
> aren't exactly the latest thing in hardware terms, it's just been a long
> road to getting them supported. Infrastructure like Mark's PM QoS work
> and Raphael's PM domains work has really helped a lot here.
Indeed, now that I checked some earliest SoC TRMs even the simplest systems
have some sort of intermediate Idle states.
>>> patches in mailing lists that show how to un-require it. Make it more
>>> painful to avoid PM_RUNTIME, and less painful to use it.
>
>> Yeah, makes a lot of sense. With new code there is no issue, only the code
>> with long history is sort of troublesome.
>
> It's mostly a transition management issue I think. When I repost I'll
> add an additional patch on top which moves the clock gating into the
> runtime PM callbacks, that way the decision on that doesn't block the
> system wide work.
Sounds like a great resolution to the problem, thanks for considering it.
And sorry for disturbing. Let's see what's Kukjin's opinion on that.
next prev parent reply other threads:[~2012-01-23 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 18:46 [PATCH] i2c-s3c2410: Add stub runtime power management Mark Brown
[not found] ` <1327171600-5489-1-git-send-email-broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-21 21:25 ` Sylwester Nawrocki
[not found] ` <4F1B2D40.70202-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-21 21:33 ` Mark Brown
2012-01-22 12:59 ` Sylwester Nawrocki
2012-01-22 15:22 ` Mark Brown
[not found] ` <20120122152234.GA2915-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-22 17:22 ` Sylwester Nawrocki
2012-01-22 17:27 ` Bill Gatliff
2012-01-22 17:48 ` Sylwester Nawrocki
2012-01-22 21:39 ` Mark Brown
2012-01-23 20:19 ` Sylwester Nawrocki [this message]
[not found] ` <20120122213952.GA29022-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-02-13 23:31 ` Ben Dooks
[not found] ` <20120213233139.GJ2999-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>
2012-02-14 0:37 ` 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=4F1DC0D3.4070408@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=ben-linux@fluff.org \
--cc=bgat@billgatliff.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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).