RD Babiera 94c9c1ac86 usb: handle displayport debounce timer empty reads ... If the device is unplugged then plugged before mDisplayPortDebounceTimer triggers, then the new displayPortPollWork could process the trigger in the intial epoll handling loop. Because the timer can be rearmed, the timerfd read results in -EAGAIN because no data is ready, but stale data was ready to begin with. Disarm the debounce timer when displayPortPollWork closes to prevent new work threads from reading timer when not ready. Also log debounce read errors as a warning and not an error. Test: manual test on device Bug: 328553922 Change-Id: Icf3dbe929eb9f0520941a4efe3dcea79a71d46c3 Signed-off-by: RD Babiera <rdbabiera@google.com>		2024-03-19 18:34:02 +00:00
..
gadget	usb: Runtime search the i2c path	2024-01-30 17:56:51 +00:00
usb	usb: handle displayport debounce timer empty reads	2024-03-19 18:34:02 +00:00