summary refs log tree commit diff
path: root/protos
diff options
context:
space:
mode:
authorDaniel Verkamp <dverkamp@chromium.org>2019-05-07 14:19:23 -0700
committerCommit Bot <commit-bot@chromium.org>2019-06-05 19:19:10 +0000
commit3bebfa29dc4185b2f3d2752ac16b0f6639548a4a (patch)
tree61c5a481f92b2791e68740078ddf9d79dfae096b /protos
parenta3411eaac1ad3d51d5282d1462d6764ad539ce13 (diff)
downloadcrosvm-3bebfa29dc4185b2f3d2752ac16b0f6639548a4a.tar
crosvm-3bebfa29dc4185b2f3d2752ac16b0f6639548a4a.tar.gz
crosvm-3bebfa29dc4185b2f3d2752ac16b0f6639548a4a.tar.bz2
crosvm-3bebfa29dc4185b2f3d2752ac16b0f6639548a4a.tar.lz
crosvm-3bebfa29dc4185b2f3d2752ac16b0f6639548a4a.tar.xz
crosvm-3bebfa29dc4185b2f3d2752ac16b0f6639548a4a.tar.zst
crosvm-3bebfa29dc4185b2f3d2752ac16b0f6639548a4a.zip
usb: reset backend device on port reset
This enables the full firmware update/reset/use device in application
mode sequence for Edge TPU USB Accelerator.

There is a bit of a UI hiccup: once the firmware update and reset is
complete, the device re-enumerates with a different VID/PID, and the
"Connect to Linux" prompt shows up again.  The user must re-affirm that
the device should be connected to Linux to proceed with using the Edge
TPU.  This may be unavoidable - I'm not sure if we can tell the
difference between a newly-inserted device and a reset one.

Allowing USBDEVFS_DISCONNECT_CLAIM should be safe, since it can only
operate on file descriptors passed into the xhci device jail.

BUG=chromium:831850
TEST=Run Edge TPU Accelerator demo and verify that it can update FW

Change-Id: I3d61c7bd914830ce25448b1ae4d60e1c16f10aed
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1599881
Reviewed-by: Zach Reizner <zachr@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Diffstat (limited to 'protos')
0 files changed, 0 insertions, 0 deletions