From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH/RFC] platform_bus: Allow runtime PM by default
Date: Sat, 27 Mar 2010 19:41:40 +0000 [thread overview]
Message-ID: <251AAFA3-F44D-40D2-BF99-E82EE58FD52D@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201003262335.06941.rjw@sisk.pl> (sfid-20100326_223222_633980_AC596020)
On 26 Mar 2010, at 22:35, "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> On Friday 26 March 2010, Mark Brown wrote:
>> Currently the default runtime PM callbacks for platform devices
>> return
>> -ENOSYS, preventing the use of runtime PM platforms until they have
>> provided at least a default implementation. This hinders the use of
>> runtime PM by devices which work with many platforms such as memory
>> mapped devices, MFDs and on chip IPs shared by multiple
>> architectures.
>>
>> Change the default implementation to the standard pm_generic_runtime
>> one, allowing drivers to use runtime PM without per-architecture
>> changes.
>>
>> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
> Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
>
> Is it very urgent?
Not especially - worst case you just don't get devices suspending
which isn't the end of the world and there's no build time
dependencies introduced.
>
> Rafael
>
>
>> ---
>>
>> I'm not 100% sure why the curret implementation returns -ENOSYS -
>> I've
>> got a horrible feeling I might be breaking something somewhere.
>>
>> drivers/base/platform.c | 6 +++---
>> 1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
>> index 43479a9..eb0f8d9 100644
>> --- a/drivers/base/platform.c
>> +++ b/drivers/base/platform.c
>> @@ -967,17 +967,17 @@ static int platform_pm_restore_noirq(struct
>> device *dev)
>>
>> int __weak platform_pm_runtime_suspend(struct device *dev)
>> {
>> - return -ENOSYS;
>> + return pm_generic_runtime_suspend(dev);
>> };
>>
>> int __weak platform_pm_runtime_resume(struct device *dev)
>> {
>> - return -ENOSYS;
>> + return pm_generic_runtime_resume(dev);
>> };
>>
>> int __weak platform_pm_runtime_idle(struct device *dev)
>> {
>> - return -ENOSYS;
>> + return pm_generic_runtime_idle(dev);
>> };
>>
>> #else /* !CONFIG_PM_RUNTIME */
>>
>
next prev parent reply other threads:[~2010-03-27 19:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 17:42 Mark Brown
2010-03-26 22:35 ` Rafael J. Wysocki
2010-03-27 19:41 ` Mark Brown [this message]
2010-03-27 23:32 ` Rafael J. Wysocki
2010-04-22 23:53 ` Greg KH
2010-04-23 10:57 ` Mark Brown
2010-04-23 15:05 ` Greg KH
2010-04-23 15:13 ` Mark Brown
2010-04-23 15:49 ` Greg KH
2010-04-23 15:57 ` Mark Brown
2010-04-23 16:11 ` Greg KH
2010-04-23 16:28 ` Mark Brown
2010-04-23 16:36 ` Greg KH
2010-04-23 16:40 ` Rafael J. Wysocki
2010-04-23 18:26 ` Rafael J. Wysocki
2010-04-23 18:41 ` Rafael J. Wysocki
2010-05-07 13:27 ` Mark Brown
2010-05-07 14:20 ` Jean Delvare
2010-05-10 21:10 ` Rafael J. Wysocki
2010-05-11 6:19 ` Jean Delvare
2010-05-11 13:00 ` [linux-pm] " 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=251AAFA3-F44D-40D2-BF99-E82EE58FD52D@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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®