Nothing the kernel can do about, because qcom's perfd is chief in charge for cpu freqs.
Recently, I tried to allow the sd821 soc to use all freqs of LITTLE (perfd is always resetting the 2188800 MHz to 1593xxx MHz). This dirty hack allowed me to unleash the 2188800 MHz:
https://github.com/nvertigo/android...mmit/37776166b1aace58f66efd94720c6ac9b95357ce
https://github.com/nvertigo/android...mmit/b83122bcd94648955c49888f3cc21420f135d934
Basically you write your upper freq limits to /sys/module/msm_performance/parameters/cpu_max_freq and remove all write bits from that file.
If rooted you can easily do that on the command line (remember to use echo with redirection instead of write) to check, if it works for your values as well. If it's working you need to modify your bootimage or try to utilize init.d or /data/local/userinit.sh (if supported by your rom).
This is no kernel or kernelmanager app issue.
@franciscofranco: I don't know your keenelmanager, but I guess you write the new max value to scaling_max_freq. Sadly this is always rewritten when libqti-perfd.so write to /sys/module/msm_performance/parameters/cpu_max_freq. This is hardcoded in the shared lib:
Code:
ingo@adler /usr/local/src/oxygenos $ strings system/vendor/lib*/libqti-perfd.so |grep 1593
0:1593600 1:1593600 2:2342400 3:2342400
0:1593600 1:1593600 2:2342400 3:2342400
ingo@adler /usr/local/src/oxygenos $
Perhaps it is possible in your app to make /sys/module/msm_performance/parameters/cpu_max_freq writable write the new max to it and drop the write permission again.