summaryrefslogtreecommitdiffstats
path: root/drivers/usb/musb/musb_cppi41.c
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2016-09-16 16:24:26 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-09-16 16:29:41 +0200
commit08c5cd37480f59ea39682f4585d92269be6b1424 (patch)
treeef69ed0b3c7f5805ac80eba1d9b01ccd6be2046d /drivers/usb/musb/musb_cppi41.c
parentusb: musb: Fix tusb6010 compile error on blackfin (diff)
downloadlinux-08c5cd37480f59ea39682f4585d92269be6b1424.tar.xz
linux-08c5cd37480f59ea39682f4585d92269be6b1424.zip
USB: change bInterval default to 10 ms
Some full-speed mceusb infrared transceivers contain invalid endpoint descriptors for their interrupt endpoints, with bInterval set to 0. In the past they have worked out okay with the mceusb driver, because the driver sets the bInterval field in the descriptor to 1, overwriting whatever value may have been there before. However, this approach was never sanctioned by the USB core, and in fact it does not work with xHCI controllers, because they use the bInterval value that was present when the configuration was installed. Currently usbcore uses 32 ms as the default interval if the value in the endpoint descriptor is invalid. It turns out that these IR transceivers don't work properly unless the interval is set to 10 ms or below. To work around this mceusb problem, this patch changes the endpoint-descriptor parsing routine, making the default interval value be 10 ms rather than 32 ms. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Tested-by: Wade Berrier <wberrier@gmail.com> CC: <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/usb/musb/musb_cppi41.c')
0 files changed, 0 insertions, 0 deletions