[KERNEL] [Nougat] [Voltage Control] Kawori Kernel for Oneplus 2 (r7, 2017/08/16)

[Billy_Wisher]

Could you please add underclocking to 302MHz on both clusters?

 

[aviraxp]

Could you please add underclocking to 302MHz on both clusters?

Underclocking breaks boot for me. I believe it is because of some scheduler stuff I added, but cannot dig further.

 

[chxei]

i didn't agreed people talking about slow charging but now i'm with lates aosp extended and stock kernel charges much faster ?

 

[CertifiedBlyndGuy]

Could you please add underclocking to 302MHz on both clusters?

Not only does it break boot but Googles own performance engineer, Tim Murray, has even gone to the point of overclocking the big cluster on Angler. I don't think that's a good idea for UX

 

[aviraxp]

Hopefully r7 willbe released tomorrow. Many changes related to cpufreq, interactive governor, scheduler, power management and more. Thanks a lot to @CertifiedBlyndGuy for his help on these.

 

[CertifiedBlyndGuy]

Hopefully r7 willbe released tomorrow. Many changes related to cpufreq, interactive governor, scheduler, power management and more. Thanks a lot to @CertifiedBlyndGuy for his help on these.

Thank you as well for correcting the mistakes I make. I appreciate it

 

[Billy_Wisher]

Not only does it break boot but Googles own performance engineer, Tim Murray, has even gone to the point of overclocking the big cluster on Angler. I don't think that's a good idea for UX

But it does work fine on AICP 12.1 kernel, no UX troubles, also it has overclocking and the only trouble is heating (but not for me)

 

[aviraxp]

r7 is uploaded. Many changes.

 

[playkish]

where from I get the Change log ?

 

[aviraxp]

where I get the Changes log ?

Github. The code speaks itself. I don't want to write too many about them and I don't like the ****ty change log like "improve general performance" that others might like.

 

[chxei]

the phone freezed and crashed 10 times already, no uv, no oc. rom aex4.5 kernel r7. no other mods installed.

---------- Post added at 18:28 ---------- Previous post was at 18:28 ----------

edit: now bootlooped

 

[ciber05]

@aviraxp does this release have the CPU driver that automatically turns off big cores while screen off? Thanks for the release!

 

[aviraxp]

the phone freezed and crashed 10 times already, no uv, no oc. rom aex4.5 kernel r7. no other mods installed.

---------- Post added at 18:28 ---------- Previous post was at 18:28 ----------

edit: now bootlooped

give me your files under /sys/fs/pstore.I can see no reason for this.

 

[aviraxp]

@aviraxp does this release have the CPU driver that automatically turns off big cores while screen off? Thanks for the release!

Sorry, nope. The reason is really simple, I cannot fix a big bug that the tunables will get mis-resumed.

 

[CertifiedBlyndGuy]

But it does work fine on AICP 12.1 kernel, no UX troubles, also it has overclocking and the only trouble is heating (but not for me)

Hmm... Google perf engineers own word, and Qualcomm spec versus application... I'm sure it works, but the scheduler is designed to shift tasks on the system level to the little cores as well as basic input boost functionality that on occasion is offloaded to the big cluster (hence why Google actually clocked it higher on Angler). This is due to the fact that the cortex-a53s are way less power hungry (they consume a maximum of 60mW at their topmost frequency making them very effecient), BUT perf on the a53s, simply put, sucks which is why they are assigned to system tasks. These cores already run at a very low 384mhz, and yet can still handle system level tasks, and basic input applications. For good UX, the large cluster MUST have at least two of the a57s running at all times... Obviously you don't want to offload much to them which is why more work is assigned to the a53s otherwise those tasks cause the frequencies of the a57 cores to ramp up greatly impacting the power cost.

So in short, yes, I am sure 302mhz works in some cases... BUT there is a reason that Qualcomm didn't clock the chips lower to begin with, and that my friend is what we call idle balancing as far as the scheduler is concerned

I hope I enlightened and that you understand more of how the scheduler and task allocation works in actual practice.

Sort of a side note, but Qualcomm chips are clocked way higher than they need to be in terms of the maximum frequency... Usually clocking down 300mhz is still good for UX without impacting perf while increasing battery life... Just a tip. But no, I wouldn't mess with the lower end spectrum of frequencies.

 

[aviraxp]

I will be away for a week guys. The kernel is complitiable for the newest los. See ya.

 

[aviraxp]

Just found out that los provides a custom power hal which resets corectl config every time screen turns on or off. Gonna replace the hal next time if los does not change it because it will ruin custom settings.

 

[chxei]

give me your files under /sys/fs/pstore.I can see no reason for this.

that folder is empty

 

[aviraxp]

that folder is empty

....Then I don't know. Sorry but I won't behave like other devs which will say "I will look at it", I don't know anything about this.

 

[chxei]

....Then I don't know. Sorry but I won't behave like other devs which will say "I will look at it", I don't know anything about this.

maybe you try that rom and than guess what can be cause? no? well, not a big deal, anyway o is coming and rebase will be needed