diff options
author | Alan Stern <stern@rowland.harvard.edu> | 2012-11-07 10:31:30 -0500 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-01-17 08:51:22 -0800 |
commit | 828b18866ce0907fdb67afe143d5d851deb9fec6 (patch) | |
tree | 535626cc8ab742a056df4acef9d6509397f4661c /CREDITS | |
parent | ede3e03c6d28bc3aca30206995fec585031698af (diff) | |
download | linux-3.10-828b18866ce0907fdb67afe143d5d851deb9fec6.tar.gz linux-3.10-828b18866ce0907fdb67afe143d5d851deb9fec6.tar.bz2 linux-3.10-828b18866ce0907fdb67afe143d5d851deb9fec6.zip |
USB: fix endpoint-disabling for failed config changes
commit 36caff5d795429c572443894e8789c2150dd796b upstream.
This patch (as1631) fixes a bug that shows up when a config change
fails for a device under an xHCI controller. The controller needs to
be told to disable the endpoints that have been enabled for the new
config. The existing code does this, but before storing the
information about which endpoints were enabled! As a result, any
second attempt to install the new config is doomed to fail because
xhci-hcd will refuse to enable an endpoint that is already enabled.
The patch optimistically initializes the new endpoints' device
structures before asking the device to switch to the new config. If
the request fails then the endpoint information is already stored, so
we can use usb_hcd_alloc_bandwidth() to disable the endpoints with no
trouble. The rest of the error path is slightly more complex now; we
have to disable the new interfaces and call put_device() rather than
simply deallocating them.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Reported-and-tested-by: Matthias Schniedermeyer <ms@citd.de>
CC: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions