Sergey Volk b5769ac1f1 Fix permissions for dp_hotplug_error_code sysfs node ... DisplayPort kernel driver passes error code/status to hardware composer via the dp_hotplug_error_code sysfs file. When HWC receives/consumes the error, it will write "0" into that file to reset the error code. So this file must be readable and writable by the HWC code running with "system" user/group permissions. Previously we used to set the ownership to system:system, but in order to be more consistent with the rest of sysfs files in that directory, we can use root:graphics instead with permissions 0664. HWC runs under the "graphics" group, so this should allow HWC write access. Bug: 324953626 Test: checked permissions of dp_hotplug_error_code sysfs Change-Id: Idf65acc12d158a78565c41f4e2aea24362e2cdff		2024-02-14 00:58:35 +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	Merge "usb: report displayport capable port partner disconnect to drm" into main	2024-01-23 17:42:41 +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