aboutsummaryrefslogtreecommitdiffstats
path: root/libmincrypt/sha.c
diff options
context:
space:
mode:
authorJack Pham <jackp@codeaurora.org>2013-12-23 17:46:10 -0800
committerPaul Kocialkowski <contact@paulk.fr>2014-05-03 17:47:13 +0200
commit575cf1967920539ad790c3c600fae2b18b9640e0 (patch)
treebc1e15dc12a72c3f42014e8b2f87120701cb4a7e /libmincrypt/sha.c
parent4744d3ecf61aea4e511b4d36a88198ae92ed3ee5 (diff)
downloadsystem_core-575cf1967920539ad790c3c600fae2b18b9640e0.tar.gz
system_core-575cf1967920539ad790c3c600fae2b18b9640e0.tar.bz2
system_core-575cf1967920539ad790c3c600fae2b18b9640e0.zip
adbd: Don't close/reopen FFS ep0 on disconnect
In case of bulk read/write failure or disconnect, transport_usb calls usb_ffs_kick in order to force the daemon to re-open the FunctionFS ep files as a way to soft restart the kernel driver. However, there's no reason to always close the ep0 file, as it would need to be reopened and the descriptors rewritten--this is unnecessary, especially in the simple/frequent case of cable disconnect, and causes the kernel driver to unbind and bind *all* of the function drivers. This is causing USB Chapter 9 tests to fail. Thus, try to reuse the same ep0 file handle across reconnects. In case there is a failure, the ep1/ep2 opens would fail and all the file handles get dropped. For the adb root case, the entire daemon gets restarted anyway. Change-Id: I0840085c52a0795dcb2d751c39aa4a436c039ee2
Diffstat (limited to 'libmincrypt/sha.c')
0 files changed, 0 insertions, 0 deletions