From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>,
"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] [RFC] PCI: Runtime power management
Date: Fri, 14 Aug 2009 19:13:56 +0200 [thread overview]
Message-ID: <200908141913.56884.rjw@sisk.pl> (raw)
In-Reply-To: <200908141905.32766.rjw@sisk.pl>
On Friday 14 August 2009, Rafael J. Wysocki wrote:
> On Friday 14 August 2009, Alan Stern wrote:
> > On Thu, 13 Aug 2009, Matthew Garrett wrote:
> >
> > > On Thu, Aug 13, 2009 at 11:22:44AM -0400, Alan Stern wrote:
...
> > > Though perhaps the device level runtime_idle shouldn't be void - that
> > > way the bus can ask the driver whether its suspend conditions have been
> > > satisfied? Right now there doesn't seem to be any way for the bus to ask
> > > that.
> >
> > If you want to get the device-level runtime_idle involved, you can make
> > _it_ responsible for scheduling the suspend. Then the bus-level code
> > simply has to check whether everything is okay at the bus level, and if
> > it is, call the device-level routine.
> >
> > However changing the return type wouldn't hurt anything, and it would
> > allow the pm_schedule_suspend call to be centralized in the bus code.
> > You could ask Rafael about it, or just send him a patch.
>
> Well, I'm not against that, but what should pm_runtime_idle() do with the
> result returned by it? Just pass it to the caller?
Hm, perhaps its better to ignore it, though.
Rafael
next prev parent reply other threads:[~2009-08-14 17:13 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 14:25 [PATCH] PM: Introduce core framework for run-time PM of I/O devices (rev. 14) Rafael J. Wysocki
2009-08-09 21:13 ` [PATCH update] PM: Introduce core framework for run-time PM of I/O devices (rev. 15) Rafael J. Wysocki
2009-08-12 10:37 ` Magnus Damm
2009-08-12 15:47 ` Alan Stern
2009-08-12 20:13 ` Rafael J. Wysocki
2009-08-13 0:29 ` [RFC] PCI: Runtime power management Matthew Garrett
2009-08-13 0:35 ` [RFC] usb: Add support for runtime power management of the hcd Matthew Garrett
2009-08-13 12:16 ` [linux-pm] " Oliver Neukum
2009-08-13 12:30 ` Matthew Garrett
2009-08-13 14:26 ` Oliver Neukum
2009-08-13 21:42 ` Matthew Garrett
2009-08-13 15:22 ` Alan Stern
2009-08-13 21:47 ` Matthew Garrett
2009-08-13 15:17 ` [RFC] PCI: Runtime power management Alan Stern
2009-08-13 21:47 ` Matthew Garrett
2009-08-14 12:30 ` [linux-pm] " Matthew Garrett
2009-08-14 14:43 ` Alan Stern
2009-08-14 17:05 ` Rafael J. Wysocki
2009-08-14 17:13 ` Rafael J. Wysocki [this message]
2009-08-14 19:01 ` Alan Stern
2009-08-14 20:05 ` Rafael J. Wysocki
2009-08-14 22:21 ` Matthew Garrett
2009-08-15 14:18 ` Rafael J. Wysocki
2009-08-15 15:53 ` Alan Stern
2009-08-15 20:54 ` Rafael J. Wysocki
2009-08-15 20:58 ` Matthew Garrett
2009-08-15 21:21 ` Rafael J. Wysocki
2009-08-15 21:27 ` Matthew Garrett
2009-08-15 21:44 ` Rafael J. Wysocki
2009-08-16 16:09 ` Alan Stern
2009-08-16 15:57 ` Alan Stern
2009-08-16 16:04 ` Matthew Garrett
2009-08-16 15:50 ` Alan Stern
2009-08-14 17:37 ` Jesse Barnes
2009-08-14 19:15 ` Rafael J. Wysocki
2009-08-14 21:22 ` Rafael J. Wysocki
2009-08-14 22:30 ` Matthew Garrett
2009-08-15 14:41 ` Rafael J. Wysocki
2009-08-15 15:24 ` Rafael J. Wysocki
2009-08-13 20:56 ` [PATCH update 2x] PM: Introduce core framework for run-time PM of I/O devices (rev. 16) Rafael J. Wysocki
2009-08-13 21:03 ` Paul Mundt
2009-08-13 21:14 ` Rafael J. Wysocki
2009-08-14 9:08 ` Magnus Damm
2009-08-14 17:19 ` Rafael J. Wysocki
2009-08-14 17:25 ` [PATCH update 3x] PM: Introduce core framework for run-time PM of I/O devices (rev. 17) Rafael J. Wysocki
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=200908141913.56884.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=stern@rowland.harvard.edu \
/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®