This is a note to let you know that I've just added the patch titled
usb: host: isp116x: use new USB_RESUME_TIMEOUT
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
usb-host-isp116x-use-new-usb_resume_timeout.patch
and it can be found in the queue-3.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 8c0ae6574ccfd3d619876a65829aad74c9d22ba5 Mon Sep 17 00:00:00 2001
From: Felipe Balbi <balbi@xxxxxx>
Date: Fri, 13 Feb 2015 14:50:10 -0600
Subject: usb: host: isp116x: use new USB_RESUME_TIMEOUT
From: Felipe Balbi <balbi@xxxxxx>
commit 8c0ae6574ccfd3d619876a65829aad74c9d22ba5 upstream.
Make sure we're using the new macro, so our
resume signaling will always pass certification.
Signed-off-by: Felipe Balbi <balbi@xxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/usb/host/isp116x-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/usb/host/isp116x-hcd.c
+++ b/drivers/usb/host/isp116x-hcd.c
@@ -1488,7 +1488,7 @@ static int isp116x_bus_resume(struct usb
spin_unlock_irq(&isp116x->lock);
hcd->state = HC_STATE_RESUMING;
- msleep(20);
+ msleep(USB_RESUME_TIMEOUT);
/* Go operational */
spin_lock_irq(&isp116x->lock);
Patches currently in stable-queue which might be from balbi@xxxxxx are
queue-3.10/usb-host-xhci-use-new-usb_resume_timeout.patch
queue-3.10/usb-host-sl811-use-new-usb_resume_timeout.patch
queue-3.10/usb-define-a-generic-usb_resume_timeout-macro.patch
queue-3.10/usb-host-isp116x-use-new-usb_resume_timeout.patch
queue-3.10/usb-gadget-composite-enable-besl-support.patch
queue-3.10/usb-host-r8a66597-use-new-usb_resume_timeout.patch
queue-3.10/usb-core-hub-use-new-usb_resume_timeout.patch
queue-3.10/usb-phy-find-the-right-match-in-devm_usb_phy_match.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html