This reverts commit 63ba0cb1affa83446f10585d403c81cc618be71a.
Reason for revert: Tentatively trying to address, http://b/193588301 OTA full package does not exist in O6/R4_SD1A.210714.001 userdebug build [SD1A]
Bug: 193588301
Change-Id: I9d5d9fc132bc7eaf7c0adccee7a18558d80edb40
We have seen cases SF main thread running longer occasionally which may
run in danger of missing frames. This CL lifts cpufreq for SF when touch
boost is active to compensate the sudden jump of its cpu demand.
Bug: 192099706
Test: Build
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: I49b2d589249f60a38eab907afbadfbcfdd233d1c
Use prebuilt GKI boot.img for production builds.
Debug builds continue to use their own Image.lz4.
Bug: 191764119
Change-Id: I2b4950ce334cc990e858e0ea410ad7e57d6decf6
Allow to thermalhal to update trip points for neutral_therm which is the
triggering sensor of virtual skin sensor for o6 proto.
Bug: 193373779
Test: neutral_therm can be updated to the correct threshold
Change-Id: I16dcd44ce9e69f456df322664756dc74357bf50b
Launcher prop needs to be accessed in system partition only,
hence move the related prop to /system/build.prop
Bug: 192621663
Test: ro.launcher.blur.appLaunch prop is set correctly,
and Blurs are disabled on App launch.
Change-Id: I6721d59498c5d35dfd560f429b8aed7a01ac29fc
* Latest is determined by alphabetical order
* To find the .cpa file, unzip the bug report and run `tar -xvf dumpstate_board.bin`
* The .cpa file can then be found under the `camera/` directory
* This can be disabled with the prop `vendor.camera.debug.camera_performance_analyzer.attach_to_bugreport`
Bug: 191169822
Test: `adb bugreport`, unzip, `tar -xvf dumpstate_board.bin`, find expected .cpa file
Change-Id: Ie05e8d446588cebea46492b267491065161915a1
init.usb.configfs.rc has the same trigger condition of midi function.
Rename the config name to "charger" to avoid triggerring twice of the
midi function.
Bug: 188744218
Test: USB enumerated in charger mode
Signed-off-by: Kyle Tso <kyletso@google.com>
Change-Id: Ica112fb4be66356901f6d5f21b79b9e648d49f35
During Tuscany runs, the Camera HAL is requesting a CAMERA_LAUNCH power
hint, which runs big and small CPU clusters at FMAX for 1 second. This is
overkill for Tuscany, so we are requesting that the hint be removed.
Tuscany should only boost during the computationally expensive image
processing, and should stop boosting as soon as a decision is reached.
This CL adds a new power hint for Tuscany. The other CLs in this topic
use this hint to boost CPU frequency during the critical section of
Tuscany by adding a call from the FaceHAL to the PowerHAL.
Running camera open and camera close without CAMERA_LAUNCH hint saves a
measured ~1W of power. The common case for this boost in Tuscany will be
a few frames at ~60ms per frame, so much less than 1 second of boost.
The worst case scenario is falsing - no attempted unlock. We will allow
the hint to time out after 1 second in that case, but that case is less
common.
Measured latency improvement per-frame from running the CPU at FMAX is
~15ms per frame. Power measurements can be found at go/tuscany-power.
NOTE: This change will _reduce_ the power/battery impact of Tuscany by
boosting for a more precise window of time.
Bug: 190755782
Test: E2E testing, validating frequency in systrace.
Change-Id: Ibca2687d2dffa4e3d2d23a9a588a2eae0b225952
All devices use gralloc4 now, so this code is unused.
Bug: 174998182
Test: builds for the affected devices
Change-Id: Icff36a0204f7f9fd10ae7269248aef8a08c5fc1e
Setting backend thread affinity with higher uclamp value can cause
governor to clock little cores to max. Disable explicit affinity for
driver backend threads.
Fixes: 192486236
Test: build, see SF's backend threads on mid cores in gpu comp.
Change-Id: Id1b17d9783fc65f2d2541fa9c6166d771494cd42
Add powerhint configuration to use CPU 4-7 when CAMERA_LAUNCH
Bug: 188369995
Test: 1. Check camera daemon move to CPU 4-7 when camera launch
2. P21 Camera Test Checklist done
Change-Id: I6ddc9ce664166c5b78c9a5bc427c800f0714b6ea
