This is a note to let you know that I've just added the patch titled
uas: Limit qdepth to 32 when connected over usb-2
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:
uas-limit-qdepth-to-32-when-connected-over-usb-2.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 <[email protected]> know about it.
>From e2875c33787ebda21aeecc1a9d3ff52b3aa413ec Mon Sep 17 00:00:00 2001
From: Hans de Goede <[email protected]>
Date: Fri, 1 Aug 2014 17:33:08 +0200
Subject: uas: Limit qdepth to 32 when connected over usb-2
From: Hans de Goede <[email protected]>
commit e2875c33787ebda21aeecc1a9d3ff52b3aa413ec upstream.
Some jmicron uas chipsets act up (they disconnect from the bus) when sending
more then 32 commands to them at once.
Rather then building an ever growing list with usb-id based quirks for
devices using this chipset, simply reduce the qdepth to 32 when connected
over usb-2. 32 should be plenty to keep things close to maximum
possible throughput on usb-2.
Tested-and-reported-by: Laszlo T. <[email protected]>
Signed-off-by: Hans de Goede <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/usb/storage/uas.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/usb/storage/uas.c
+++ b/drivers/usb/storage/uas.c
@@ -1026,7 +1026,7 @@ static int uas_configure_endpoints(struc
usb_endpoint_num(&eps[3]->desc));
if (udev->speed != USB_SPEED_SUPER) {
- devinfo->qdepth = 256;
+ devinfo->qdepth = 32;
devinfo->use_streams = 0;
} else {
devinfo->qdepth = usb_alloc_streams(devinfo->intf, eps + 1,
Patches currently in stable-queue which might be from [email protected] are
queue-3.16/xhci-blacklist-using-streams-on-the-etron-ej168-controller.patch
queue-3.16/uas-limit-qdepth-to-32-when-connected-over-usb-2.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
