USB: Dealias -110 code (more complete)
The purpose of this patch is to split off the case when a device does not reply on the lower level (which is reported by HC hardware), and a case when the device accepted the request, but does not reply at upper level. This redefinition allows to diagnose issues easier, without asking the user if the -110 happened "immediately". The usbmon splits such cases already thanks to its timestamp, but it's not always available. I adjusted all drivers which I found affected (by searching for "urb"). Out of tree drivers may suffer a little bit, but I do not expect much breakage. At worst they may print a few messages. Signed-off-by: Pete Zaitcev <zaitcev@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
ec17cf1cfe
commit
38e2bfc94e
@@ -294,11 +294,6 @@ static int interpret_urb_result(struct us_data *us, unsigned int pipe,
|
||||
return USB_STOR_XFER_ERROR;
|
||||
return USB_STOR_XFER_STALLED;
|
||||
|
||||
/* timeout or excessively long NAK */
|
||||
case -ETIMEDOUT:
|
||||
US_DEBUGP("-- timeout or NAK\n");
|
||||
return USB_STOR_XFER_ERROR;
|
||||
|
||||
/* babble - the device tried to send more than we wanted to read */
|
||||
case -EOVERFLOW:
|
||||
US_DEBUGP("-- babble\n");
|
||||
|
Reference in New Issue
Block a user