This is a note to let you know that I've just added the patch titled
usb: dwc2/gadget: do not call disconnect method in pullup
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-do-not-call-disconnect-method-in-pullup.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 b510df5a36c066da3a188f4ade3404118b63c6de Mon Sep 17 00:00:00 2001
From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
Date: Tue, 9 Sep 2014 10:44:11 +0200
Subject: usb: dwc2/gadget: do not call disconnect method in pullup
From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
commit b510df5a36c066da3a188f4ade3404118b63c6de upstream.
This leads to potential spinlock recursion in composite framework, other
udc drivers also don't call it directly from pullup method.
Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
Signed-off-by: Robert Baldyga <r.baldyga@xxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/usb/dwc2/gadget.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/usb/dwc2/gadget.c
+++ b/drivers/usb/dwc2/gadget.c
@@ -2943,7 +2943,6 @@ static int s3c_hsotg_pullup(struct usb_g
s3c_hsotg_phy_enable(hsotg);
s3c_hsotg_core_init(hsotg);
} else {
- s3c_hsotg_disconnect(hsotg);
s3c_hsotg_phy_disable(hsotg);
}
Patches currently in stable-queue which might be from m.szyprowski@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-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