RD Babiera 523717b768 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 (cherry-picked from 94c9c1ac86f398c22ddc446f17bd7ab3fddb675c) Change-Id: Icf3dbe929eb9f0520941a4efe3dcea79a71d46c3 Signed-off-by: RD Babiera <rdbabiera@google.com>		2024-03-19 18:35:19 +00:00
..
Android.bp	Revert^2 "usb: introduce UsbDataSessionMonitor class"	2023-12-08 20:15:27 +00:00
android.hardware.usb-service.rc	Fix permissions for dp_hotplug_error_code sysfs node	2024-02-14 00:58:35 +00:00
android.hardware.usb-service.xml	usb: update usb hal version to v3	2023-11-14 20:41:47 +00:00
service.cpp	Branch zuma from gs201	2022-04-19 12:45:55 +08:00
Usb.cpp	usb: handle displayport debounce timer empty reads	2024-03-19 18:35:19 +00:00
Usb.h	usb: report displayport capable port partner disconnect to drm	2023-12-11 22:34:53 +00:00
UsbDataSessionMonitor.cpp	usb: dump flag value in the constructor	2024-01-10 08:50:07 +00:00
UsbDataSessionMonitor.h	usb: implement heuristics to flag data compliance warnings	2023-12-26 22:25:25 +00:00