Considering strict power management for mobile device, we should also power off the usb controller if there are no slaves attached even though it is usb host function, but it will meet usb device resume failure in below situation. Suppose that no slave attached ----> usb interface runtime suspend ----> usb device runtime suspend -----> xhci suspend -----> power off usb controller. After that if the system wants to enter suspend state, then it also will issue usb_dev_suspend(), then the pm_runtime_resume() issued in choose_wakeup() function will return '-ESHUTDOWN' due to xhci has been suspend and hardware is not accessible. After system entering resume state, if there is slave attached ----> power on usb controller ----> xhci resume ----> usb device runtime resume ----> usb interface runtime resume. But usb device will resume failed if runtime errors is set ('-ESHUTDOWN'), thus we should clear the runtime errors in choose_wakeup() function to avoid this situation. Signed-off-by: Baolin Wang <baolin.wang@xxxxxxxxxx> --- changes since v1: - Modify the changelog to explain clearly. - Remove 'ret' variable in choose_wakeup(). --- drivers/usb/core/driver.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c index dadd1e8d..bce283c 100644 --- a/drivers/usb/core/driver.c +++ b/drivers/usb/core/driver.c @@ -1431,8 +1431,11 @@ 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) { + if (pm_runtime_resume(&udev->dev) == -ESHUTDOWN) + pm_runtime_set_suspended(&udev->dev); + } + udev->do_remote_wakeup = w; } -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html