perfd is not working as the following error on our device
[0: perfd: 955] devbw soc:qcom,cpubw: dev_pm_opp_get_opp_count: device OPP not found (-19)
So I reverted all the perfd stuffs
This reverts commit 21dcb08866.
Maybe sometimes the governor properties are not set properly so add this
line to enable CPU 0 explicitly
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Then this power HAL will optimize the schedutil properties by a hint
from the device condition.
By the way, is this feature corrupted on LG devices where I got the
power HAL from? Why they don't edit this string?
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Set up_rate_limit_us to 250 and down_rate_limit_us 10000 unlike
schedutil that uses 500 and 20000 repectively. The new values are from
lge_msm8996-common.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
The configs are set for interactive, not EAS. So we have to edit those
configs to be based on EAS system.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
I imported sched_boost implement to my custom kernel, which is for HMP system
basically but to use the CAF power optimizations we should have that node.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
As our power HAL only can work when if perfd exists, we have to import this
binary from another device.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
blu_schedutil is basically from the Pixel 3 kernel, and I did import
this to my custom kernel. This has been developed for the better battery
performance based on schedutil.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
The msm_irqbalance configuration of lge_msm8996-common has more IRQ
numbers for excepting mdss and kgsl-3d0. This is good to improve UX stability.
Refers:
d5f348aedd
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
As we're building our power HAL ourselves, the
TARGET_POWERHAL_SET_INTERACTIVE_EXT flag doesn't working at all. So I
merged this feature to our power HAL to use the extension works, which
is disabling S-Pen panel, LCD, hardware touch key power.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
By copying files from LineageOS/android_device_lge_msm8996-common, it is
more proper for supporting EAS.
Refers:
- ca20a0d81e
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I55cfcb3b764059aac81d265529bdb979c6334f45
This also resolves my workaround for building kernel,
780bb8553c
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: Ia6baaa3f2055206f7e21fbf97d2616b03b95ff79
This is used by the new "virtual disk" feature used by vold to help
debug and test storage code on devices without physical media.
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I89c9263f4d1843a751f39fb5c7d7d2150267a295
Update of the commit 24df69b
Confirmed this working with clean installation
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I21ddd66000d18fa93a77e1eb6714f1ae6fd7f0b2
Seems settings this to true breaks unlocking process sometimes on our
device
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I0e1f9bd260e62f76a06c5cca2576c5d925c9b91c
Ours somewhat contaminated for Samsung specific setups. So I removed all
the stock media configs and import them from
LineageOS/android_device_oneplus_oneplus3
Signed-off-by: Deokgyu Yang <secugyu@gmail.com>
Change-Id: I36cbc17d0f6da25733b4d4bc9c57469ddf0fb866
