public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: stefan.koch10@gmail.com, stern@rowland.harvard.edu,
	oneukum@suse.com, falakreyaz@gmail.com, broonie@kernel.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: core: Add runtime resume checking
Date: Tue, 9 Aug 2016 12:26:31 +0200	[thread overview]
Message-ID: <20160809102631.GA30327@kroah.com> (raw)
In-Reply-To: <653c8e893d4de1ab4dcade2ca2da9f2cfe369c2c.1470735102.git.baolin.wang@linaro.org>

On Tue, Aug 09, 2016 at 05:33:33PM +0800, Baolin Wang wrote:
> When the usb device has entered suspend state by runtime suspend method, and
> the sustem also try to enter suspend state by issuing usb_dev_suspend(), it
> will issue pm_runtime_resume() function to deal with wrong wakeup setting in
> choose_wakeup() function.
> 
> But if usb device resumes failed due to xhci has been into suspend state and
> hardware is not accessible, which will set runtime errors. Thus when there is
> slave attached, usb device will resume failed by runtime resume method due to
> previous runtime errors.

I really can't parse the first sentance in this paragraph, what exactly
makes xhci so "unique" here?

> Then we should check if it resumes successfully in choose_wakeup() function,

what is "it"?

> if it failed we should clear the runtime errors by pm_runtime_set_suspended()
> function to avoid runtime resume failure.

Again, what is "it"?

> 
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
> ---
>  drivers/usb/core/driver.c |    9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c
> index dadd1e8d..a1a0f5f 100644
> --- a/drivers/usb/core/driver.c
> +++ b/drivers/usb/core/driver.c
> @@ -1412,6 +1412,7 @@ static int usb_resume_both(struct usb_device *udev, pm_message_t msg)
>  static void choose_wakeup(struct usb_device *udev, pm_message_t msg)
>  {
>  	int	w;
> +	int	ret;
>  
>  	/* Remote wakeup is needed only when we actually go to sleep.
>  	 * For things like FREEZE and QUIESCE, if the device is already
> @@ -1431,8 +1432,12 @@ static void choose_wakeup(struct usb_device *udev, pm_message_t msg)
>  	/* If the device is autosuspended with the wrong wakeup setting,
>  	 * autoresume now so the setting can be changed.
>  	 */
> -	if (udev->state == USB_STATE_SUSPENDED && w != udev->do_remote_wakeup)
> -		pm_runtime_resume(&udev->dev);
> +	if (udev->state == USB_STATE_SUSPENDED && w != udev->do_remote_wakeup) {
> +		ret = pm_runtime_resume(&udev->dev);
> +		if (ret == -ESHUTDOWN)
> +			pm_runtime_set_suspended(&udev->dev);

why is 'ret' needed:
		if (pm_runtime_resume(&udev->dev) == -ESHUTDOWN)


Why would resume fail?

thanks,

greg k-h

  reply	other threads:[~2016-08-09 10:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  9:33 [PATCH] usb: core: Add runtime resume checking Baolin Wang
2016-08-09 10:26 ` Greg KH [this message]
2016-08-10  2:33   ` Baolin Wang
2016-08-10  6:18     ` Peter Chen
2016-08-10  6:43       ` Baolin Wang
2016-08-10  9:07         ` Peter Chen
2016-08-10  9:35           ` Baolin Wang
2016-08-10 14:25             ` Alan Stern
2016-08-11  3:08               ` Baolin Wang
2016-08-11  6:54                 ` Peter Chen
2016-08-11  8:07                   ` Baolin Wang
2016-08-11  8:19                     ` Peter Chen
2016-08-11  8:41                       ` Baolin Wang
2016-08-11  8:44                         ` Peter Chen
2016-08-11  9:08                           ` Baolin Wang
     [not found]     ` <20160810081707.GB7753@kroah.com>
2016-08-10  8:23       ` Baolin Wang

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=20160809102631.GA30327@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=baolin.wang@linaro.org \
    --cc=broonie@kernel.org \
    --cc=falakreyaz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stefan.koch10@gmail.com \
    --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