From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: System sleep vs. runtime PM
Date: Sat, 12 Dec 2009 23:45:35 +0100 [thread overview]
Message-ID: <200912122345.35288.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0912121411230.12891-100000@netrider.rowland.org>
On Saturday 12 December 2009, Alan Stern wrote:
> On Sat, 12 Dec 2009, Rafael J. Wysocki wrote:
>
> > > Also, when the system resume is finished, drivers need a chance to
> > > runtime-suspend again. Hence the pm_runtime_put_noidle() call in
> > > dpm_complete() should be changed to pm_runtime_put_sync().
> >
> > OK
> >
> > Are you going to send a patch or do you want me to prepare one?
>
> We're talking about mostly documentation changes, right? I can write
> them.
OK
> But the code changes will present a small problem. I'll need them for
> the USB development. Will it be okay to ask Greg KH to put them in his
> tree after you have accepted them into yours? That will avoid
> cross-subsystem build errors. (We just got through one of them
> involving David Miller and I'd rather avoid any more.)
I'm fine with that.
> There's one other thing (should have brought it up earlier): Do you
> mind having the runtime-PM callbacks invoke the bus type or the bus
I guess you mean device type and device class?
> class methods instead of the bus methods, if they are defined? That
> is, do them in the same way the system-PM callbacks work. The USB code
> will definitely want different methods for the different types. In
> fact, I've already written a version that tests the bus type within the
> callback routines.
That's a good question. I didn't anticipate that, so it's hard to tell right
now. I don't really see any fundamental obstacles now, though.
Rafael
next prev parent reply other threads:[~2009-12-12 22:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 15:37 System sleep vs. runtime PM Alan Stern
2009-12-12 17:33 ` Rafael J. Wysocki
2009-12-12 19:22 ` Alan Stern
2009-12-12 22:45 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-02 18:35 Alan Stern
2009-12-02 21:16 ` Oliver Neukum
2009-12-02 22:20 ` Alan Stern
2009-12-02 23:02 ` Oliver Neukum
2009-12-03 0:19 ` Rafael J. Wysocki
2009-12-03 16:53 ` Alan Stern
2009-12-03 15:25 ` Alan Stern
2009-12-03 17:13 ` Oliver Neukum
2009-12-03 17:50 ` Alan Stern
2009-12-03 19:34 ` Oliver Neukum
2009-12-03 19:52 ` Alan Stern
2009-12-03 20:11 ` Oliver Neukum
2009-12-03 20:33 ` Alan Stern
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=200912122345.35288.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=greg@kroah.com \
--cc=linux-pm@lists.linux-foundation.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