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: Mon, 30 Nov 2009 22:06:27 +0100	[thread overview]
Message-ID: <200911302206.27960.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0911301132520.4478-100000@iolanthe.rowland.org>

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?

Rafael


> ---
> 
> Index: usb-2.6/drivers/base/power/runtime.c
> ===================================================================
> --- usb-2.6.orig/drivers/base/power/runtime.c
> +++ usb-2.6/drivers/base/power/runtime.c
> @@ -703,16 +703,22 @@ EXPORT_SYMBOL_GPL(pm_request_resume);
>   * @dev: Device to handle.
>   * @sync: If set and the device is suspended, resume it synchronously.
>   *
> - * Increment the usage count of the device and if it was zero previously,
> - * resume it or submit a resume request for it, depending on the value of @sync.
> + * Increment the usage count of the device.  If @sync is set, resume the device
> + * and wait for the resume to complete.  Otherwise if the device is currently
> + * suspending or suspended, submit a resume request.
> + *
> + * If @sync is clear, the caller is responsible for synchronization.
>   */
>  int __pm_runtime_get(struct device *dev, bool sync)
>  {
> -	int retval = 1;
> -
> -	if (atomic_add_return(1, &dev->power.usage_count) == 1)
> -		retval = sync ? pm_runtime_resume(dev) : pm_request_resume(dev);
> +	int retval = 0;
>  
> +	atomic_inc(&dev->power.usage_count);
> +	if (sync)
> +		retval = pm_runtime_resume(dev);
> +	else if (dev->power.runtime_status == RPM_SUSPENDING ||
> +	    dev->power.runtime_status == RPM_SUSPENDED)
> +		retval = pm_request_resume(dev);
>  	return retval;
>  }
>  EXPORT_SYMBOL_GPL(__pm_runtime_get);
> Index: usb-2.6/Documentation/power/runtime_pm.txt
> ===================================================================
> --- usb-2.6.orig/Documentation/power/runtime_pm.txt
> +++ usb-2.6/Documentation/power/runtime_pm.txt
> @@ -276,8 +276,9 @@ drivers/base/power/runtime.c and include
>      - increment the device's usage counter
>  
>    int pm_runtime_get(struct device *dev);
> -    - increment the device's usage counter, run pm_request_resume(dev) and
> -      return its result
> +    - increment the device's usage counter; if the device is currently
> +      suspending or suspended then run pm_request_resume(dev) and return its
> +      result
>  
>    int pm_runtime_get_sync(struct device *dev);
>      - increment the device's usage counter, run pm_runtime_resume(dev) and

  reply	other threads:[~2009-11-30 21:06 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 [this message]
2009-11-30 22:03   ` Alan Stern
2009-11-30 22:17     ` Rafael J. Wysocki
2009-12-01 23:09     ` Rafael J. Wysocki
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=200911302206.27960.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