From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.org>, Magnus Damm <damm@igel.co.jp>,
linux-pm@lists.linux-foundation.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>
Subject: Re: [patch update] PM: Introduce core framework for run-time PM of I/O devices
Date: Tue, 16 Jun 2009 01:21:39 +0200 [thread overview]
Message-ID: <200906160121.40843.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0906151700570.2643-100000@iolanthe.rowland.org>
On Monday 15 June 2009, Alan Stern wrote:
> On Mon, 15 Jun 2009, Rafael J. Wysocki wrote:
>
> > On Sunday 14 June 2009, Rafael J. Wysocki wrote:
> > > On Sunday 14 June 2009, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
> > > > Below is the current version of my "run-time PM for I/O devices" patch.
> > > >
> > > > I've done my best to address the comments received during the recent
> > > > discussions, but at the same time I've tried to make the patch only contain
> > > > the most essential things. For this reason, for example, the sysfs interface
> > > > is not there and it's going to be added in a separate patch.
> > > >
> > > > Please let me know if you want me to change anything in this patch or to add
> > > > anything new to it. [Magnus, I remember you wanted something like
> > > > ->runtime_wakeup() along with ->runtime_idle(), but I'm not sure it's really
> > > > necessary. Please let me know if you have any particular usage scenario for
> > > > it.]
> >
> > Appended is an update of the patch addressing the today's comments from Magnus.
>
> This is really looking very good. I'll do a more detailed review
> later. (In particular, I have not checked the details of the rather
> intricate state machine transitions.) For now, a couple of things
> struck my eye:
>
> Shouldn't the calls to complete() really be complete_all()? There
> might be more than one thread waiting for a suspend or resume callback
> to finish.
Yes, thanks for pointing that out.
> Since pm_runtime_resume() takes care of powering up the parent, there's
> no need for pm_request_resume() to worry about it also.
But still it won't hurt to do it IMO, because the parents are then going to be
resumed before our pm_runtime_resume() is called.
> The documentation should mention that the runtime_suspend method is
> supposed to enable remote wakeup if it as available and if
> device_may_wakeup(dev) is true.
Well, I thought that was obvious. :-)
Best,
Rafael
next prev parent reply other threads:[~2009-06-15 23:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 22:23 [PATCH] PM: Introduce core framework for run-time PM of I/O devices Rafael J. Wysocki
2009-06-14 9:41 ` Magnus Damm
2009-06-14 10:29 ` Rafael J. Wysocki
2009-06-14 9:58 ` [linux-pm] " Rafael J. Wysocki
2009-06-14 22:57 ` [patch update] " Rafael J. Wysocki
2009-06-14 23:18 ` Arjan van de Ven
2009-06-15 20:02 ` Rafael J. Wysocki
2009-06-15 21:08 ` Alan Stern
2009-06-15 23:21 ` Rafael J. Wysocki [this message]
2009-06-16 14:30 ` Alan Stern
2009-06-16 21:30 ` [patch update 2] " Rafael J. Wysocki
2009-06-16 22:33 ` [patch update 2 fix] " Rafael J. Wysocki
2009-06-17 20:08 ` Alan Stern
2009-06-17 23:07 ` Rafael J. Wysocki
2009-06-18 18:17 ` Alan Stern
2009-06-19 0:38 ` Rafael J. Wysocki
2009-06-19 16:25 ` Alan Stern
2009-06-19 22:42 ` Rafael J. Wysocki
2009-06-20 2:34 ` Alan Stern
2009-06-20 14:30 ` [linux-pm] " Alan Stern
2009-06-20 23:48 ` Rafael J. Wysocki
2009-06-21 2:30 ` Alan Stern
2009-06-21 11:32 ` Rafael J. Wysocki
2009-06-22 14:16 ` Alan Stern
2009-06-22 15:27 ` Rafael J. Wysocki
2009-06-22 15:39 ` Alan Stern
2009-06-22 15:53 ` Rafael J. Wysocki
2009-06-22 6:20 ` Magnus Damm
2009-06-22 6:43 ` Arjan van de Ven
2009-06-22 7:27 ` Magnus Damm
2009-06-22 13:49 ` [linux-pm] " Arjan van de Ven
2009-06-22 15:39 ` Rafael J. Wysocki
2009-06-22 15:33 ` Rafael J. Wysocki
2009-06-22 8:15 ` Oliver Neukum
2009-06-20 23:38 ` [patch update 3] " Rafael J. Wysocki
2009-06-21 2:23 ` Alan Stern
2009-06-21 12:46 ` Rafael J. Wysocki
2009-06-22 15:01 ` Alan Stern
2009-06-22 15:49 ` Rafael J. Wysocki
2009-06-22 16:28 ` Alan Stern
2009-06-22 23:02 ` Rafael J. Wysocki
2009-06-23 17:02 ` Alan Stern
2009-06-23 17:45 ` Rafael J. Wysocki
2009-06-23 18:26 ` Alan Stern
2009-06-24 0:17 ` Rafael J. Wysocki
2009-06-24 14:51 ` Alan Stern
2009-06-24 19:14 ` Rafael J. Wysocki
2009-06-24 20:19 ` Alan Stern
2009-06-24 21:23 ` Rafael J. Wysocki
2009-06-24 15:04 ` [patch update] " Pavel Machek
2009-06-27 21:52 ` Rafael J. Wysocki
2009-07-06 8:28 ` Pavel Machek
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=200906160121.40843.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=damm@igel.co.jp \
--cc=gregkh@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=oliver@neukum.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