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: I4b179de4ce3b178c069a9a12e9ba2dee2cdeb23f
Revert submission 22606975-turn off qs
Reason for revert: confirm with team that this CL submit too early and need to rollback then submit again at 4/19.
Reverted changes: /q/submissionid:22606975-turn+off+qs
Change-Id: I24d478f4d49d0e1685e3ad797d6b3bc97967f1a6
am skip reason: Merged-In I2ade29622e6c01ade96a7b15609131635c7ac502 with SHA-1 b50a7c52a7 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2528310
Change-Id: Ied5909dd55ce8976e02df7e191fd507fb3f37cfa
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I2ade29622e6c01ade96a7b15609131635c7ac502 with SHA-1 b50a7c52a7 is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2528310
Change-Id: I7a383f3ee31ab8f7ac8a55adeba94b3cd65a80cc
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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: I873b6abe4b05f2d3c74fe7e84b634390be779506
The ufs script is to work for ffu preparing. If device's ufs has an
old firmware, the script will copy the valid firmware into disk and
wait for ffu update on bootloader.
Bug: 273305212
Test: full build and test ffu update
Change-Id: Ib5e2c57494ee22c33b93f1eda0e72049dcd12d16
Signed-off-by: Leo Liou <leoliou@google.com>
am skip reason: Merged-In Ic83c61df6297696c06e63a23241b308f92ac70bd with SHA-1 588ebb3a8f is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2486736
Change-Id: Id010420fb540974fcaa66796ecff2407b127c73f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ic83c61df6297696c06e63a23241b308f92ac70bd with SHA-1 588ebb3a8f is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2486736
Change-Id: Iba8c895f0cb45b4b3141bbd7c6601bdc9070f8a9
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ic83c61df6297696c06e63a23241b308f92ac70bd with SHA-1 588ebb3a8f is already in history
Original change: https://android-review.googlesource.com/c/device/google/bluejay/+/2486736
Change-Id: Ie9a3fbd6589d2bc1d3fa5da7ebfb10404b8c5b99
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
