When exiting camera app, camera daemon is still busy in background,
which may affect the launch animation of launcher. So, limit the cpuset
of camera daemon to little cores for 1 second when there is app launch
hint to improve it. This only happens when camera is running. Also bypass this behavior when video recording is active.
Bug: 240889279
Test: camera daemon cpuset changed as expected
Change-Id: I130b1e4718f8e5ef47ad761a2a73d86697d0f8bc
This CL increases min MIF frequency to 1352000 in 30fps mode.
Although the MIF power consumption increases due to this
change, but the reduction in CPU cycles results in over-all SoC
power saving. This change also doesn't negatively impact framedrop
rate.
P22 change is ag/19820773.
Bug: 256564865
Test: Build pass, GCA, Camera power and performance evaluation
Change-Id: Iacf9172f0ce9edeecb14d38edc3c1466e7e4c7fe
- CPU/GPU more aggressive throttling
Bug: 248392264
Test: boot to home and thermal throttling worked properly
Change-Id: Idfa7ec21877a11000d2c6d17e4bbcabc9606f58c
Fine-tune the util threshold to "1100 1078 1024"
Bug: 243729855
Test: Build pass, GCA, 60fps recording power and performance test
Change-Id: I4a348127b913aa4783f69ba468be1fd77f784def
INTERACTION is removed but some actions still use it.
Bug: 246738037
Test: pts-tradefed run commandAndExit pts -m PtsPerformanceTestCases -t
com.google.android.perf.pts.PowerHintJsonVerifyTest
Change-Id: Id7028106ac7ff1d41dc7d325aad5fa4d69bc2a54
With systemui now changed its cpuset in early stage, we no longer
need RestrictedCpuset hint as workaround.
Bug: 242775562
Test: build pass
Change-Id: I8075188e82295f45fb7df1a88769eef37e7aec81
Allow these devices to send CPU hints to PowerHAL from SF to reduce
drops and save power.
Bug: b/241152899
Bug: b/195990840
Test: https://android-build.googleplex.com/builds/abtd/run/L70800000956157278
Change-Id: I81df99f4ec01f417d1589e2323de599819993590
(Port from commit 8a419466b86ab07a25fc18d7d6a2a9ee154f6839)
This CL sets the MIF min clock frequency to 1539MHz, which based on
initial ODPM and MIPS measurements shows benefit both in terms of power
consumption and cycles-per-instructions (CPI), reducing the gap with R4
device.
L10 power and performance impact tests will update on the bug.
Bug: 239651545
Test: Build pass, GCA
Change-Id: I1b057f187e45bad46f4661bd5673f0f88aab3a93
1) Change the default trip_point_1_temp and trip_point_2_temp in accordance to new config provided by hardware.
2) Removing AUR nodes
Bug: 233329602
Test: Used local build to verify the trip_point_1_temp & trip_point_2_temp when VIRTUAL_SKIN
severity is changed on updating quiet_therm temp.
Change-Id: I267032c23c22952e5eea106ca3b84a8cd74729a0
Update target load due to Pro mid CPU
this hint impact the high streaming use case like 60fps / 120fps and
240fps.
Bug: 236682655
Test: GCA
Change-Id: I0f486e44267d30efa12b6c30ebf1d7aea8989892
we need disable uclamp_threshold and reduce_prefer_idle, boost FG group when apps launch and remove FPS based hints for TA boost.
Bug: 233423618
Test: build pass
Signed-off-by: chungkai <chungkai@google.com>
Change-Id: I3fe9318d46426c1e5ef7defe85126501313d419f
Disable the powerhint for F2FS gc_urgent mode, since we are going to
replace this with the smart idle maintenance service.
Test: turn on/off the screen & check /sys/fs/f2fs/dm-*/gc_urgent
Bug: 214430685
Signed-off-by: Daeho Jeong <daehojeong@google.com>
Change-Id: Ia07ea20078c82f62cc450fd2b0fade83a65e66ae
P21 has been using GPU power hold during app launch to mitigate jank
from GPU power on latency.
However this same mechanism seems causing instability (may be related
to the new inter-frame power optimization). While the root cause is
being investigated, disable the boost.
Bug: 223828284
Test: Build
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: Id04a1d09ebd5b36c1c7c55824da34bffb6435cab
Fork the powerhint.json from gs201 and align the config with panther
Bug: 207573241
Test: build and boot pass
Change-Id: Ic517f1cd5462f3653de3742834ec251362e7849d
