Keiichi Watanabe c59db48131 devices: vvu: Unbind driver first regardless of driver type ... When a VVU driver starts, the current implementation tries to unbind virtio-pci driver unconditionally, but this can fail when no driver is bounded or another driver is bounded. Instead of assuming virtio-pci driver is bounded, we should unbind the bounded driver regardless of its type by writing to "/sys/bus/pci/devices/${ADDR}/driver/unbind", which is a symlink to the unbind file of the currently bounded driver. This change will allow the vvu driver to open a vvu device after a previous driver exists. (Note that our vvu device hasn't supported reinitialization yet.) BUG=b:216407443 TEST=run vvu on workstation Change-Id: Ib6c3ac1cd51a8018573596eef9fe0fd759450c07 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3581833 Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Abhishek Bhardwaj <abhishekbh@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>		2022-04-13 02:27:28 +00:00
..
src	devices: vvu: Unbind driver first regardless of driver type	2022-04-13 02:27:28 +00:00
Cargo.toml	devices: Upstream Windows vhost-user net device.	2022-04-07 01:19:21 +00:00