public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] PM: allow for usage_count > 0 in pm_runtime_get()
Date: Wed, 2 Dec 2009 00:09:57 +0100	[thread overview]
Message-ID: <200912020009.57496.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0911301659460.4478-100000@iolanthe.rowland.org>

On Monday 30 November 2009, Alan Stern wrote:
> On Mon, 30 Nov 2009, Rafael J. Wysocki wrote:
> 
> > On Monday 30 November 2009, Alan Stern wrote:
> > > This patch (as1308) fixes __pm_runtime_get().  Currently the routine
> > > will resume a device if the prior usage count was 0.  But this isn't
> > > right; thanks to pm_runtime_get_noresume() the usage count can be
> > > positive even while the device is suspended.
> > > 
> > > Now the routine always tries to carry out a resume when called
> > > synchronously.  When called asynchronously, it avoids the overhead of
> > > an unnecessary spinlock acquisition by doing the resume only if the
> > > device's state was SUSPENDING or SUSPENDED.
> > > 
> > > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> > 
> > All three patches applied to suspend-2.6/linux-next.  Do you want me to push
> > them to Linus before 2.6.32, or perhaps the $subject one only?
> 
> Thanks.  The patches are not urgently needed; they can wait until the 
> merge window.
> 
> BTW, I just noticed that the runtime_idle method is documented as 
> returning void but defined in pm.h as returning int.  Obviously the 
> definition is wrong, since no return value is ever used.  Would you 
> like to fix it?

In fact it's been changed to return int at the Matthew's request, because
bus type code might use the return value from a driver's callback.  In fact
the PCI runtime PM framework being worked on at the moment uses
the return value of a driver's runtime_idle(), if implemented.

So, the documentation has to be changed rather than the definition.

Thanks,
Rafael

  parent reply	other threads:[~2009-12-01 23:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 16:35 [PATCH] PM: allow for usage_count > 0 in pm_runtime_get() Alan Stern
2009-11-30 21:06 ` Rafael J. Wysocki
2009-11-30 22:03   ` Alan Stern
2009-11-30 22:17     ` Rafael J. Wysocki
2009-12-01 23:09     ` Rafael J. Wysocki [this message]
2009-12-02 15:15       ` Alan Stern
2009-12-01 16:15   ` Alan Stern
2009-12-01 23:01     ` Rafael J. Wysocki
2009-12-02 15:13       ` 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=200912020009.57496.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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