diff options
| author | Alan Stern <[email protected]> | 2017-11-08 17:23:17 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2017-11-09 12:02:23 +0000 |
| commit | 2ef47001b3ee3ded579b7532ebdcf8680e4d8c54 (patch) | |
| tree | f18359ee963f40e6fbdf3ecac25d55c79baad293 /lib/mpi/mpi-pow.c | |
| parent | usb: core: message: remember to reset 'ret' to 0 when necessary (diff) | |
| download | kernel-2ef47001b3ee3ded579b7532ebdcf8680e4d8c54.tar.gz kernel-2ef47001b3ee3ded579b7532ebdcf8680e4d8c54.zip | |
USB: usbfs: compute urb->actual_length for isochronous
The USB kerneldoc says that the actual_length field "is read in
non-iso completion functions", but the usbfs driver uses it for all
URB types in processcompl(). Since not all of the host controller
drivers set actual_length for isochronous URBs, programs using usbfs
with some host controllers don't work properly. For example, Minas
reports that a USB camera controlled by libusb doesn't work properly
with a dwc2 controller.
It doesn't seem worthwhile to change the HCDs and the documentation,
since the in-kernel USB class drivers evidently don't rely on
actual_length for isochronous transfers. The easiest solution is for
usbfs to calculate the actual_length value for itself, by adding up
the lengths of the individual packets in an isochronous transfer.
Signed-off-by: Alan Stern <[email protected]>
CC: Minas Harutyunyan <[email protected]>
Reported-and-tested-by: wlf <[email protected]>
CC: <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-pow.c')
0 files changed, 0 insertions, 0 deletions
