I use the Programm PI Control zu monitoring my RPI2 on OSMC.
The Programm use the datei “scaling_cur_freq” to read an print the current CPU-frequency. But scaling_cur_freq say the RPI2 akually CPU-frequency are allway the higest CPU-frequenzy (900mHz). Also i use ssh and the Code “cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq” it prints for the current CPU-frequenz always 900mHz. The same as well in the systeminfo in Kodi, there only shows the maximum CPU frequency as the current CPU-frequency!
If i read the file “cpuinfo_min_freq” (“sudo cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq”) it shows my the right current CPU-frequency (600mHz or 900mHz).
Yes – it’s intentional. I mount --bind the max_freq over the current scaling frequency. This is so that user’s don’t get confused and think there system is underclocked.
ah ok, that explains a lot
Did you only bind the max_freq over the current scaling frequency for the display in Kodi or also for the “scaling_cur_freq” file?
And can i do it backward? (It find so a bit confusing and would like to see the current frequency. Also manny monitoring tools for the RPI use"scaling_cur_freq" to read the current CPU-frequency)
