And restore DownRateLimitUs to previous values as they're not compatible
without the feature being enabled.
Bug: 383127224
Bug: 383332732
Flag: EXEMPT not support for powerhints
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: Ie6cfaf4855d647337f0295f89588e426269d7b7b
Since the default value 1 is the lowest priority, it only
takes effect while all other values are disabled.
Therefore, the hints associated to value 1 are unnecessary.
Bug: 357445276
Change-Id: Ic7fdddfafc92969629cfbfd5cb4a392fe0060c3d
Flag: EXEMPT not supported by this component yet
Test: Boot to home and check the trace and ADPF profile
Test: adb shell dumpsys android.hardware.power.IPower/default
See go/pixel-perf-amm-experiment for more info.
Bug: 365855872
Test: build/flash; set .Perf__amm_experiment=true, observe auto_migration_margins_enable value changing 1->0; set .Perf__amm_experiment="", observe the value changing 0->1
Flag: NONE controlled by Mendel instead
Change-Id: Iacd310c83821cce8f50cdb82ab39f714c50f0e42
Signed-off-by: Dmitry Skiba <dskiba@google.com>
This change introduces "is APF enabled" system properties, and
uses them as trigger conditions for APF nodes / pre-APF nodes.
By default APF nodes are active, and pre-APF nodes are inactive,
which maintains the situation before this change.
A future experiment will flip "is APF enabled" system properties,
deactivating APF nodes and activating pre-APF nodes. For more
info see go/pixel-perf-apf-experiment.
Bug: 365855872
Test: set vendor.powerhal.apf_enabled=false, vendor.powerhal.apf_disabled=true, observe auto_prefer_fit
procfs value is never "1"
Flag: NONE powerhint change does not support flags
Change-Id: I919ad3ffe5f496df75bcb492bd3b4fa2285df65c
Signed-off-by: Dmitry Skiba <dskiba@google.com>
By default slow it down as auto margins can lead to faster ramping up in
low activity use cases.
Set it back to default in GAME mode to retain previous behavior. Set it
explicitly for DISPLAY_IDLE as a potential area for more tuning in the
future.
Bug: 315748906
Flag: EXEMPT powerhints are not compatible with flagging
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I1ffb04afb0911acc8aae4388e7f6478ebfc96dae
And reduce DownRateLimitUs to 500us as the system should be more
reactive now when something needs to rampup quickly.
Enable pertask iowait boost too as with auto dvfs headroom enabled all
tasks will start form 0 util_avg and this could impact iowait tasks
without this being enabled to help them migrate up to bigger cores.
Camera use cases should still use their own default DownRateLimitUs and
disable this feature to keep their dvfs_headroom tuning intact.
Bug: 315748906
Flag: EXEMPT powerhints are not compatible with flagging
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: Id8959b1debe8612623f47cdc103349ae0412a609
we already saw some janks caused by longer runnable time.
so Enable TAPreferIdle for first frame
Bug: 372168866
Flag: NONE powerhint do not support flag
Change-Id: I01f699abd1eaed5760789d6c0788cbe4791e2b13
Signed-off-by: Chungkai Mei <chungkai@google.com>
The node "/sys/kernel/vendor_mm/pa_kill/reclaim_kb" is write-only. So we need to add WriteOnly flag to prevent powerhal to read the node.
SELinux errors:
avc: denied { dac_read_search } for comm="android.hardwar" capability=2 scontext=u:r:hal_power_default:s0 tcontext=u:r:hal_power_default:s0 tclass=capability permissive=0
avc: denied { dac_override } for comm="android.hardwar" capability=1 scontext=u:r:hal_power_default:s0 tcontext=u:r:hal_power_default:s0 tclass=capability permissive=0
Bug: 350830411
Change-Id: Ic78a419b1500efce631e848d36816bc87d666920
Test: adb shell dumpsys android.hardware.power.IPower/default, check if any avc denied messages
Flag: EXEMPT config json change
- Add a event node for SYSTEM_UI;
- Add a separate SYSTEM_UI profile;
- Remove unused profiles.
Bug: 359672110
Test: adb shell dumpsys android.hardware.power.IPower/default
Flag: NONE powerhal doesn't have a flag yet
Change-Id: I9f5fa718c72c94229e23993b551592f567093dec
These streams do not disable TA or FG prefer idle, so restore it.
Bug: 236868627
Flag: NONE powerhint change does not support flags
Test: build pass
Change-Id: Iadb6f711c907e6ba25c29ac15cc1e8cb73b57684
Enable auto prefer fit for high prio tasks when app launch, and tune
uclmap min settings for different task prio.
Bug: 353885521
Flag: NONE powerhint change does not support flags
Test: build pass
Change-Id: Iad6f5d332e66dc09ed12d09e3e443144bc25c31d
This CL defines CAMERA_MULTICAM_BOOST (with the same settings as the
existing CAMERA_ZOOMING_BOOST). Having both definitions is necessary to
be able to transition from zooming boost to multicam boost. Once the
multicam boost flag is fully rolled out, we can remove the
CAMERA_ZOOMING_BOOST.
Bug: 347829135
Test: adb logcat
Flag: EXEMPT resource file only change
Change-Id: I964f40926914d5006e5440a71a288f23e594161a
Boosting kswapd's uclamp minimum value in the scheduler
allows kswapd more opportunities to remain in middle cores.
This change enhances kswapd's memory reclamation efficiency.
Bug: 351708752
Test: check kbnob value when the panel is on/off
Flag: EXEMPT device policy tuning
Change-Id: I4b75016aa3f2de22b0b9e46d8e594d4042124a04
Signed-off-by: Martin Liu <liumartin@google.com>
Also disable prefer idle for TA and FG by default.
Bug: 236868627
Flag: NONE powerhint change does not support flags
Test: build pass
Change-Id: I0c09c4ef30e10d358a71de11283dda43b4f96837
Bug: 344685639
Test: Checked the trace file running on the device.
Flag: NONE powerhal doesn't have a flag yet
Change-Id: I550086e5c47991ed25c3b988ca11e8cf9df5d118
Currently, we enable PA_KILL always on camera launch. This CL puts this
feature behind a power boost profile which can only be triggered from
camera hal and is controlled by a mendel flag.
Bug: 350594261
Test: adb logcat
Flag: EXEMPT resource only update
Change-Id: Id227bd35fda97d5b0cbdfe9e4df39eff2e565b7d
http://ag/27702721 removed value 50 from PMU_BIG_SPC_THRESHOLD. Set the
value to 20 for CAMERA_PROJECT11.
Bug: 347647774
Test: Flash on ripcurrentpro board and boot
Change-Id: I20aa20119ab8317d3ba92b8118d34f3b9e884b66
Since the system is more reactive now when tasks are getting busier, set
DownRateLimitUs to 500us to avoid increasing power.
Also enable pertask iowait boost as util_avg will always start from
0 for forked tasks and this could impact io tasks that need additional
help to ensure to migrate to bigger core if they need more perf.
Bug: 339664411
Test: PTE A/B test
Flag: NONE powerhint change does not support flags
Signed-off-by: Qais Yousef <qyousef@google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:c09bc9d8b58cc4f9bba136a1dc97b5c0b7751dce)
Merged-In: Iecbbaccc81297ee0f66f8c45299846f2415ee29c
Change-Id: Iecbbaccc81297ee0f66f8c45299846f2415ee29c
It's disabled by default.
Ensure camera and game mode explicitly disable it too as it is only
required when auto margins are enabled for now.
Ensure it is disabled when screen is off too as We don't want io
activities to cause wake up on bigger cores while screen is off.
Bug: 339664411
Test: PTE A/B test
Flag: NONE no behavior change
Signed-off-by: Qais Yousef <qyousef@google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:6e7e510a8eeace8d37836d6e428e13a61d66f0c1)
Merged-In: Icbbfb2d332b412fa51d6d434d44d1ada8545338c
Change-Id: Icbbfb2d332b412fa51d6d434d44d1ada8545338c
Everything should be disabled by default.
Make sure camera and game explicitly disable them by default too.
Ensure the feature is disable when screen is idle.
Bug: 339664411
Test: PTE A/B test
Flag: NONE no behavior change
Signed-off-by: Yvonne Yip <ykyyip@google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:a4523a214541f2cd3a079c010790c372b8058f31)
Merged-In: I3dd2bfe1824af489cd1ccc3a69557c180bf33ddf
Change-Id: I3dd2bfe1824af489cd1ccc3a69557c180bf33ddf
So that we can change the default values without impacting it.
Bug: 339664411
Test: PTE A/B test
Flag: NONE no behavior change
Signed-off-by: Qais Yousef <qyousef@google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:eb1962034f12f42907e5641a195f49456e951b31)
Merged-In: I8ca117bba2e0b59802de5fb19eae507548ff0a6e
Change-Id: I8ca117bba2e0b59802de5fb19eae507548ff0a6e
Reducing CPUDVFSHeadroom can help save power in 60fps and 240fps
use-cases once RT threads are enabled. Even without the RT patch
(ag/27725456), we can see savings without any impact to framedrop rate.
Bug: 341495529
Test: https://docs.google.com/document/d/14djeCdDIjDy9wqtYc4C9OPnp7sOx3HfbQz4dIZarvVE
Change-Id: Ib16a52d83669c5e9705d80c48b7097e102cc807f
