From 945f9e6cd5775b49c284ebcc6204a46e46407295 Mon Sep 17 00:00:00 2001 From: Hua Cheng Date: Mon, 14 Nov 2022 13:48:56 +0000 Subject: [PATCH 1/3] Revert "[Steadiface] Disable landmark inference dsp usage." This reverts commit f7f4d8e84f71a825df2caee074c589daaa4b2ae9. Reason for revert: The issue b/255244818 caused by cl/476717338 is fixed in cl/477452462 on QPR2. Bug: 257660234 Test: CTS Test: Check DSP-TPU landmark is enabled. Change-Id: I122b3d786cf670515fc471baa043fdd4ccdf0d72 --- device.mk | 1 - 1 file changed, 1 deletion(-) diff --git a/device.mk b/device.mk index aa184c6f..05aa9d22 100644 --- a/device.mk +++ b/device.mk @@ -657,7 +657,6 @@ PRODUCT_DEFAULT_PROPERTY_OVERRIDES += debug.sf.earlyGl.app.duration=16600000 PRODUCT_DEFAULT_PROPERTY_OVERRIDES += debug.sf.frame_rate_multiple_threshold=120 PRODUCT_DEFAULT_PROPERTY_OVERRIDES += debug.sf.layer_caching_active_layer_timeout_ms=1000 PRODUCT_DEFAULT_PROPERTY_OVERRIDES += debug.sf.treat_170m_as_sRGB=1 -PRODUCT_DEFAULT_PROPERTY_OVERRIDES += persist.vendor.camera.sf_usedsp=0 PRODUCT_DEFAULT_PROPERTY_OVERRIDES += ro.surface_flinger.enable_layer_caching=true PRODUCT_DEFAULT_PROPERTY_OVERRIDES += ro.surface_flinger.set_idle_timer_ms?=80 From 4e3f62823d75c1062910d585fa538ad3822f8546 Mon Sep 17 00:00:00 2001 From: Cynthia Wasonga Date: Thu, 10 Nov 2022 22:58:53 +0000 Subject: [PATCH 2/3] Prevent preinstallation of AOSP apps on gs201 for clone profile Bug: 238970256 Test: build Change-Id: Ie275257ce334d914437125afdc4a7e9350208266 --- device.mk | 1 + ...ed-packages-product-gs201-device-debug.xml | 35 +++++++++++++++++++ 2 files changed, 36 insertions(+) create mode 100644 preinstalled-packages-product-gs201-device-debug.xml diff --git a/device.mk b/device.mk index 2a65977d..807f05f8 100644 --- a/device.mk +++ b/device.mk @@ -901,6 +901,7 @@ PRODUCT_PACKAGES += ShannonIms #RCS Test Messaging App PRODUCT_PACKAGES_DEBUG += \ + preinstalled-packages-product-gs201-device-debug.xml \ TestRcsApp PRODUCT_PACKAGES += ShannonRcs diff --git a/preinstalled-packages-product-gs201-device-debug.xml b/preinstalled-packages-product-gs201-device-debug.xml new file mode 100644 index 00000000..a0b67c36 --- /dev/null +++ b/preinstalled-packages-product-gs201-device-debug.xml @@ -0,0 +1,35 @@ + + + + + + + + + + + + + + + + + + + From 0f9dcda5199a10053b69f68a5470f6db7a7b8f95 Mon Sep 17 00:00:00 2001 From: Vaibhav Devmurari Date: Mon, 21 Nov 2022 17:47:38 +0000 Subject: [PATCH 3/3] Allow system server to access sysfs node of led lights. To support input device lights manager feature in frameworks, provide sysfs node access to system server process. DD: go/pk_backlight_control (For keyboard backlight control for external keyboards) Similar CL: ag/20102346 Kernel provides a standardized LED interface to expose LED controls over sysfs: https://docs.kernel.org/leds/leds-class.html The feature will be provided for devices with kernel sysfs class led support and vendor kernel driver for input controllers that do have lights. The kernel sysfs class led support is a kernel config option (LEDS_CLASS), and an input device driver will create the sysfs class node interface. By giving system_server the access to these sysfs nodes, the feature will work on devices with the kernel option and kernel input/hid driver support. We do use CTS tests to enforce the kernel options and the input device drivers. What's already supported: - We already expose paths for UHID based LED nodes which covers all bluetooth based peripherals that have custom vendor drivers to expose LED sysfs nodes. (see CL aosp/1546377) What's included in this CL: - Exposing paths for sysfs nodes for external USB based devices that expose LED nodes using vendor specific drivers using standard LED interface provided by Kernel - We are using specific paths for USB devices instead of /sys/class/leds to avoid giving access to system LED nodes that would also appear under /sys/class/leds (see discussion in aosp/1546377) NOTE: Light HAL should never touch the HID device sysfs light, as the light HAL only defines a number of lights supported (https://android.googlesource.com/platform/hardware/interfaces/+/master/light/2.0/types.hal) but not include input device lights, so we shouldn't have conflict for managing these lights. NOTE: External keyboard backlight is different for HAL light type KEYBOARD which is for devices with attached keyboards. Test: manual Bug: 245506418 Change-Id: I17031179b7c1e56b0e841d4047859006d005fd21 --- conf/ueventd.gs201.rc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/conf/ueventd.gs201.rc b/conf/ueventd.gs201.rc index 6a33ec9f..a7ff48c3 100644 --- a/conf/ueventd.gs201.rc +++ b/conf/ueventd.gs201.rc @@ -222,3 +222,9 @@ # ODPM /sys/bus/iio/devices/iio:device* enabled_rails 0660 system system + +# sysfs LED nodes for external USB devices +/sys/devices/platform/11210000.usb/11210000.dwc3/xhci-hcd-exynos.5.auto/usb2/2-1/*/*/leds/* brightness 0664 system system +/sys/devices/platform/11210000.usb/11210000.dwc3/xhci-hcd-exynos.5.auto/usb2/2-1/*/*/leds/* multi_intensity 0664 system system +/sys/devices/platform/11210000.usb/11210000.dwc3/xhci-hcd-exynos.4.auto/usb2/2-1/*/*/leds/* brightness 0664 system system +/sys/devices/platform/11210000.usb/11210000.dwc3/xhci-hcd-exynos.4.auto/usb2/2-1/*/*/leds/* multi_intensity 0664 system system