From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.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: Sun, 22 Jan 2012 18:48:36 +0100 [thread overview]
Message-ID: <4F1C4BF4.5040409@gmail.com> (raw)
In-Reply-To: <CADkCAusScak6gH4BBowrOpveGG=eDjZdj+X8vF4D5+yi8gv5PA@mail.gmail.com>
Hi,
On 01/22/2012 06:27 PM, Bill Gatliff wrote:
> On Sun, Jan 22, 2012 at 6:22 PM, Sylwester Nawrocki
> <sylvester.nawrocki@gmail.com> wrote:
>> The best solution would be to force platform to enable PM_RUNTIME if
>> they want to use a driver which does runtime PM. But this has to wait,
>> yet, probably infinitely.. :)
>
> Probably easier to motivate platforms to enable PM_RUNTIME if there
> are drivers that require it. :)
>
> 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.
> 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.
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-01-22 17:48 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 [this message]
2012-01-22 21:39 ` Mark Brown
2012-01-23 20:19 ` Sylwester Nawrocki
[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=4F1C4BF4.5040409@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).