If auto rotation is enabled, it will trigger LAUNCH hint while
camera is running if device rotates, which could limit camera_hal
tasks to little cores. So, disable it first until there is a new
hint for the rotation event.
Bug: 297273578
Test: build pass
Change-Id: I104bdf8952da66346ecf73ed02245b8bc4be3ee8
Camera is highly optimized in launched devices, so that we disable idle balancer to avoid influencing previous optimization.
Bug: 281489720
Change-Id: I210f5c14ec589b06e8d8e80799cf7cb650baa9c5
Signed-off-by: Chungkai Mei <chungkai@google.com>
For the current design, thermalHAL will only enable one hint base on the current severity and disable the previous one. As a result, the power hint of higher severity should maintain the actions from lower severity which cause the larger config size and maintenance effort.
The new thermalHAL design will keep the lower severity's hint enabled, so we could remove the duplicate policies from higher level.
Bug: 241737737
Test: verified T6pro with emul_temp
Change-Id: I82d84e1e085b1a22284aa913606b40f219583210
Bug: 280258727
Test: Found regression in b/286002292, local test.
Change-Id: I6024d1a1d669809d7ed8401d66e4ac8facd3112a
Signed-off-by: paulsu <paulsu@google.com>
Reduce StaleTimeFactor for power saving
Bug: 269523712
Test: boot and run uibench
Change-Id: I106a4a2322a93147205e079c9461619967a33917
Signed-off-by: Ziyi Cui <ziyic@google.com>
util_threshold only controls migration margin now. dvfs headroom has its
own new knob.
Bug: 261705301
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I4223b3984003369e8fc7b2f0eac03bbe68569d6c
Upstream has fixed relationship between uclamp_min and margin which
means uclamp_min value between 80-100% of capacity of the CPU is a valid
value and will not cause upmigration.
To keep the current hints in powerhint.json the same, we must update
uclamp_min to be capacity_orig_of(medium_cpu) + 1.
This change is dependent on uclamp vs fits margin in GKI, vendor
modules. And an improvement in sched_pixel to ignore the 25% boost if
the only reason to request the frequency is uclamp_min.
To cater for the later - we multiply each uclamp_min value with 1.25
- except ones that look intentionally set around capacity boundaries.
Bug: 261695590
Test: PtsUiBench
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I1e6889ebea9877cb23708722a73e97177e6be185
Sync PMU and EM_Profile tuning changes (ag/20028064, ag/20075269 and ag/20084677) for 30fps power and performance optimization.
Bug: 265749383
Test: Build pass, GCA
Change-Id: Id45edbf77de1435559cb1171e56bee9c5a2e80b7
the file node was removed so also remove these
dummy setting
Bug: 260806701
Change-Id: I23044f7f32cf4b2b2cc93205ec5751525f05ee7f
Signed-off-by: Chungkai Mei <chungkai@google.com>
Changing cpuset itself takes time, so we should reduce the cpuset
change as possible. Since all camera streaming mode change to the
same cpuset value, we could make it default setting.
Bug: 240889279
Test: build pass
Change-Id: I4ecce69a254bf30b128b25ab59b1b69a02bfb18d
Large screen have more elements to be drew and current ADPF boost cap is
not high enough.
Raise the uclamp.min Cap from BIG 1.42GHz to BIG 1.58GHz
Raise the uclamp.min Init from MID 553MHz to MID 696GHz or BIG 500MHz
Also remove ADPF 120/90FPS config since the display only supports 60FPS
Bug: 257170078
Test: PtsUiBench & Calendar
Change-Id: I6865dd7d1237a687f62400a9720624821f342402
Camera hints was canceled at activityStop and applied the rule for
a while after LAUNCH hint, exten the LAUNCH HINT to fix it.
Bug: 255927500
Test: build and launch/exit camera
Change-Id: I86b19467f6038a7fde0935bf79f0a0e6bc76523b
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
Boost big cpu cluster when face unlock and relax
CPU minimum frequency boost for LAUNCH_CAMERA
Bug: 248960565
Change-Id: I075b7f4447327be4ef601c531b43473f79dbc74a
LAUNCH_120FPS 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: I3ab91cace52c617adf0ccadb95098de697efc5c0
1) Change the default trip_point_1_temp and trip_point_2_temp in accordance to new config provided by hardware (b/235166018#comment5).
2) Removing AUR nodes
Bug: 246546076
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: I240ba1b77706b6ce8991285dfa0ea6deae25f15b
With systemui now changed its cpuset in early stage, we no longer
need RestrictedCpuset hint as workaround.
Bug: 242775562
Test: build pass
Change-Id: I17603010b7070594f703e04b09cfb3a2a37ecac5
Allow these devices to send CPU hints to PowerHAL from SF to reduce
drops and save power.
Bug: b/241152899
Bug: b/195990840
Test: manual
Change-Id: I06a38eeade1aea7cb12bef079b555e6e34d2581c
(Port from commit 8a419466b86ab07a25fc18d7d6a2a9ee154f6839)
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: I179991c60b27edb6df518f387cbea1043548ea8d
Sync latest powerhint to unblock boot.
Bug: 235850212
Test: Boot to home
Signed-off-by: Jonglin Lee <jonglin@google.com>
Change-Id: I0369570176d962411ae1bc2b40396952e8ac205f
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
