Bug: 344685639
Test: Checked the trace file running on the device.
Flag: NONE powerhal doesn't have a flag yet
Change-Id: I8f21008a15f1805d6b193e56cdd8ba5146270e90
Heuristic boost will adjust the ADPF boost profile when the
powerhal detects the power session is very janky, providing more
boost for deadline sensitive threads managered in the session.
Bug: 341111433
Test: adb shell dumpsys android.hardware.power.IPower/default;
Check the device adpf sessions' traces.
Change-Id: I191ed6f479a8f49082d64e9fb1723884634133c7
Add the "UclampMax_EfficientBase" value to the ADPF config in the
powerhint.json to specify efficient core scheduling in the static
case, and "UclampMax_EfficientOffset" for the dynamic case, for this
device.
Bug: 277285195
Test: manual
Change-Id: I694eed1342c5becbd3161b88342cd66868ddb78b
This is part of an optimization that limits the length and prevelance of
this power hint. Strict, ultra-agression minimizes power and latency
versus always-on mid aggression.
Bug: 297964952
Change-Id: I0dac04d30e623a869be89ac6a5cfe002a64da48e
This patch is meant to reduce frame drop rate in 60FPS video recording with zoom in/out.
The boost will be triggered at 60FPS video recording while zoom ratio change (for each request that contain zoom ratio control in metadata), and will last for 15 frames.
Test: gca_smoke_test
Bug: 315102326
Change-Id: I7f0587881c131590f629dab838aa734a8b082c70
Vendor sched procfs path hierarchy gets updated in kernel.
Update the paths in powerhint json file to match the change.
Bug: 289151587
Test: UIbench ab test.
Change-Id: I9b4ac68990cd720deac7d933f1b2fc25e406cc40
Add DISPLAY_CHANGE hint for display layout change due to rotation or
switching between inner and outer panels.
Bug: 298150450
Test: build pass
Change-Id: Ic36b8b9928e9cdffce3697b5eb12cb586dcc5d7d
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: I5040ae4893632f7f7b88cb23ad45554f17fee04c
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 lynx by emul_temp
Change-Id: Icd62dcdcbc0c2651cb6522d6663bc513646bbaad
Bug: 280258727
Test: Found regression in b/286002292, local test.
Change-Id: Ief3d1bded3add877b23b4c2b211cef6d5a9eaf57
Signed-off-by: paulsu <paulsu@google.com>
Reduce StaleTimeFactor for power saving
Bug: 269523712
Test: boot and run uibench
Change-Id: I5d6c88ce46074673c87476d1dcc20c4fd9b9b1e7
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: I48d330cb7d9d82d05ec0dfc4b38ea0d8a22409aa
Use LOW_POWER power hint to detect and lower the control temp
for junction control loops.
Bug: 266011718
Test: Build and boot on device. Check thermal control temperatures
during battery save
Change-Id: If2e0756b24913ed5d71e499e219f7b60b947baaa
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: I4689a953734b6049da14ec13ef399c1c686b1024
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: I11a865fa2eeeb67225d4b129497b1cd85237644f
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
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
