It's an Orange Pi PC 1GB RAM H3 Quad Core. I think it's running at 1.37 GHz.
Something very strange hapenned when taking the screenshot. Before the capture the values are as in the first pic, but when saving the file it jumped to a higher value.
Code:
orangepipc:~:% cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 2.04 ms. hardware limits: 480 MHz - 1.37 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.10 GHz, 1.20 GHz, 1.30 GHz, 1.37 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, schedutil current policy: frequency should be within 480 MHz and 1.37 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.37 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:0.23%, 648 MHz:0.03%, 816 MHz:0.03%, 960 MHz:0.14%, 1.0 1 GHz:0.09%, 1.10 GHz:0.18%, 1.20 GHz:0.14%, 1.30 GHz:0.25%, 1.37 GHz:98.90% (7 22) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 2.04 ms. hardware limits: 480 MHz - 1.37 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.10 GHz, 1.20 GHz, 1.30 GHz, 1.37 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, schedutil current policy: frequency should be within 480 MHz and 1.37 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.37 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:0.23%, 648 MHz:0.03%, 816 MHz:0.03%, 960 MHz:0.14%, 1.0 1 GHz:0.09%, 1.10 GHz:0.18%, 1.20 GHz:0.14%, 1.30 GHz:0.25%, 1.37 GHz:98.90% (7 22) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 2.04 ms. hardware limits: 480 MHz - 1.37 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.10 GH[code][code][code]z, 1.20 GHz, 1.30 GHz, 1.37 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, schedutil current policy: frequency should be within 480 MHz and 1.37 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.37 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:0.23%, 648 MHz:0.03%, 816 MHz:0.03%, 960 MHz:0.14%, 1.0 1 GHz:0.09%, 1.10 GHz:0.18%, 1.20 GHz:0.14%, 1.30 GHz:0.25%, 1.37 GHz:98.90% (7 22) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 2.04 ms. hardware limits: 480 MHz - 1.37 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.10 GHz, 1.20 GHz, 1.30 GHz, 1.37 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, schedutil current policy: frequency should be within 480 MHz and 1.37 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.37 GHz (asserted by call to hardware). cpufreq stats: 480 MHz:0.23%, 648 MHz:0.03%, 816 MHz:0.03%, 960 MHz:0.14%, 1.0 1 GHz:0.09%, 1.10 GHz:0.18%, 1.20 GHz:0.14%, 1.30 GHz:0.25%, 1.37 GHz:98.90% (7 22)
