Take ADPF_FIRST_FRAME hint to boost the GPU freq to 302000
Bug: 243025173
Test: Manual
Change-Id: I53fabad1b16c14da7c0883bb4858b8622781b609
Merged-In: I53fabad1b16c14da7c0883bb4858b8622781b609
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
No need to prevent uclamp.min update rate by Granularity.
There is no perf impact.
Bug: 232336917
Test: /data/nativetest64/libperfmgr_test/libperfmgr_test
Change-Id: Iddbf24fd3419164028d55d0e401b5a8742136c91
Modify the path of vendor_sched nodes
Test: powerhal work normally
Signed-off-by: chungkai <chungkai@google.com>
Change-Id: If0ce170988bd75f1a284388fdcc37370a100b24b
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: I6c56412663849b4f8b9b462f095457165a1aed14
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
based on two sources:
1. 52e030ecef8a2debcd0a7cebb0b2cddc50e8e4e6
(ChangeId: Ieba6a75fe45595592c61dc5ad4e0c723adccaf35)
2. 3164f3d31b1197f305d968027f2e6f18663f1382
(ChangeId: Ic517f1cd5462f3653de3742834ec251362e7849d)
No-Typo-Check: based on above commit
Bug: 220073297
Change-Id: I244f73dc8485045e1bc4605a2701a1e4d32139b0