public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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: Sun, 28 Mar 2010 00:32:00 +0100	[thread overview]
Message-ID: <201003280032.01011.rjw@sisk.pl> (raw)
In-Reply-To: <251AAFA3-F44D-40D2-BF99-E82EE58FD52D@opensource.wolfsonmicro.com>

On Saturday 27 March 2010, Mark Brown wrote:
> 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.

OK, so I guess it will be sufficient if Greg queues it for .35.

Rafael

  reply	other threads:[~2010-03-27 23:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 17:42 [PATCH/RFC] platform_bus: Allow runtime PM by default Mark Brown
2010-03-26 22:35 ` Rafael J. Wysocki
2010-03-27 19:41   ` Mark Brown
2010-03-27 23:32     ` Rafael J. Wysocki [this message]
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=201003280032.01011.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    /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