This is a note to let you know that I've just added the patch titled
usb: dwc2/gadget: avoid disabling ep0
to the 3.16-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-dwc2-gadget-avoid-disabling-ep0.patch
and it can be found in the queue-3.16 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 604eac3c0c69e98f2fd0133305f9e777418f1d3b Mon Sep 17 00:00:00 2001
From: Robert Baldyga <r.baldyga@xxxxxxxxxxx>
Date: Tue, 9 Sep 2014 10:44:13 +0200
Subject: usb: dwc2/gadget: avoid disabling ep0
From: Robert Baldyga <r.baldyga@xxxxxxxxxxx>
commit 604eac3c0c69e98f2fd0133305f9e777418f1d3b upstream.
Endpoint 0 should not be disabled, so we start loop counter from number 1.
Signed-off-by: Robert Baldyga <r.baldyga@xxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/usb/dwc2/gadget.c
+++ b/drivers/usb/dwc2/gadget.c
@@ -2896,7 +2896,7 @@ static int s3c_hsotg_udc_stop(struct usb
return -ENODEV;
/* all endpoints should be shutdown */
- for (ep = 0; ep < hsotg->num_of_eps; ep++)
+ for (ep = 1; ep < hsotg->num_of_eps; ep++)
s3c_hsotg_ep_disable(&hsotg->eps[ep].ep);
spin_lock_irqsave(&hsotg->lock, flags);
Patches currently in stable-queue which might be from r.baldyga@xxxxxxxxxxx are
queue-3.16/usb-dwc2-gadget-fix-phy-disable-sequence.patch
queue-3.16/usb-dwc2-gadget-delay-enabling-irq-once-hardware-is-configured-properly.patch
queue-3.16/usb-dwc2-gadget-break-infinite-loop-in-endpoint-disable-code.patch
queue-3.16/usb-dwc2-gadget-do-not-call-disconnect-method-in-pullup.patch
queue-3.16/usb-dwc2-gadget-avoid-disabling-ep0.patch
queue-3.16/usb-dwc2-gadget-fix-phy-initialization-sequence.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