mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 05:03:05 +00:00
a1e0d46704
virtio-input devices can receive events from the guest. Primarily this is used controlling the numlock, capslock, and scroll lock lights. For KiwiMouse, we'll be using LED 0 (the numlock LED) to allow the guest to signal whether the mouse should be captured. We need the capture information to be communicated from the virtio-input device to SurfaceInput, but some of the plumbing is missing. Currently we only support host -> guest data, and not the other way around (at least in gpu_display_win). This CL adds a route for data to flow from virtio-input to the gpu_display_win Surface via the the GPU device worker & GpuDisplay::handle_event_device. Bug: 239991275 Test: ran emulator & verified events were arriving in on_handle_event_device as expected. Change-Id: I7ab8e5ec51f7aa655b2cb44fe38483103388b53d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4719210 Reviewed-by: Vikram Auradkar <auradkar@google.com> |
||
|---|---|---|
| .. | ||
| base_event_token_derive | ||
| src | ||
| tests | ||
| .build_test_serial | ||
| Cargo.toml | ||