XIEGU X6100のCPUクロックを変更してみた。
XIEGU X6100のCPUクロックを変更してみた。※毎度ながら通常は一般ユーザーで作業します。X6100を armbian で起動（下記の 1 Button 参照）※X6100の画面の写真が21MHzのAMになっているのは特に意味はありません。■X6100のCPU情報を表示root@x6100:~# cpufreq-infocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 480 MHz and 1.01 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.01 GHz (asserted by call to hardware). cpufreq stats: 120 MHz:0.00%, 240 MHz:0.00%, 312 MHz:0.00%, 408 MHz:0.00%, 480 MHz:0.00%, 504 MHz:0.00%, 600 MHz:0.00%, 648 MHz:0.00%, 720 MHz:0.00%, 816 MHz:0.00%, 912 MHz:0.00%, 1.01 GHz:100.00%analyzing CPU 1: driver: cpufreq-dt※以下省略現状のクロックは1.01GHzで、120 MHz - 1.01 GHzの範囲で変更できることがわかる。CPUクロックを下げて行ってX6100の画面表示に変化があるかやってみた。１．CPUクロック：1.01GHz（デフォルト）root@x6100:~# cpufreq-set -u 1.01Gcpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 480 MHz and 1.01 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.01 GHz (asserted by call to hardware). cpufreq stats: 120 MHz:17.37%, 240 MHz:0.00%, 312 MHz:0.00%, 408 MHz:0.00%, 480 MHz:0.00%, 504 MHz:0.00%, 600 MHz:0.00%, 648 MHz:0.00%, 720 MHz:4.50%, 816 MHz:0.00%, 912 MHz:6.52%, 1.01 GHz:71.62% (5)■デフォルトなので画面は変化なし２．CPUクロック：912MHzroot@x6100:~# cpufreq-set -u 912Minfocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 480 MHz and 912 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 912 MHz (asserted by call to hardware). cpufreq stats: 120 MHz:15.47%, 240 MHz:0.00%, 312 MHz:0.00%, 408 MHz:0.00%, 480 MHz:0.00%, 504 MHz:0.00%, 600 MHz:0.00%, 648 MHz:0.00%, 720 MHz:4.00%, 816 MHz:0.00%, 912 MHz:6.37%, 1.01 GHz:74.16% (6)■特に変化なし３．CPUクロック：816MHzroot@x6100:~# cpufreq-set -u 816Minfocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 480 MHz and 816 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 816 MHz (asserted by call to hardware). cpufreq stats: 120 MHz:14.90%, 240 MHz:0.00%, 312 MHz:0.00%, 408 MHz:0.00%, 480 MHz:0.00%, 504 MHz:0.00%, 600 MHz:0.00%, 648 MHz:0.00%, 720 MHz:3.86%, 816 MHz:0.64%, 912 MHz:9.16%, 1.01 GHz:71.44% (7)■画面は特に変化なし４．CPUクロック：720MHzroot@x6100:~# cpufreq-set -u 720Minfocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 480 MHz and 720 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 720 MHz (asserted by call to hardware). cpufreq stats: 120 MHz:14.40%, 240 MHz:0.00%, 312 MHz:0.00%, 408 MHz:0.00%, 480 MHz:0.00%, 504 MHz:0.00%, 600 MHz:0.00%, 648 MHz:0.00%, 720 MHz:4.58%, 816 MHz:3.12%, 912 MHz:8.85%, 1.01 GHz:69.05% (8)■画面は特に変化なし（のように見える）５．CPUクロック：504MHz（648M、600Mは省略）root@x6100:~# cpufreq-set -u 504Minfocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 480 MHz and 504 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 504 MHz (asserted by call to hardware). cpufreq stats: 120 MHz:12.94%, 240 MHz:0.00%, 312 MHz:0.00%, 408 MHz:0.00%, 480 MHz:0.00%, 504 MHz:0.62%, 600 MHz:3.64%, 648 MHz:3.48%, 720 MHz:6.53%, 816 MHz:2.80%, 912 MHz:7.96%, 1.01 GHz:62.04% (11)■画面はwaterfallの描画が少し遅くなったような気がする。６．CPUクロック：408MHz（480Mは省略）root@x6100:~# cpufreq-set -u 408Minfocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 408 MHz and 408 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 120 MHz:11.28%, 240 MHz:0.00%, 312 MHz:0.00%, 408 MHz:0.67%, 480 MHz:10.00%, 504 MHz:2.70%, 600 MHz:3.17%, 648 MHz:3.03%, 720 MHz:5.69%, 816 MHz:2.44%, 912 MHz:6.93%, 1.01 GHz:54.08% (13)■画面はwaterfallの描画が遅くなったような気がする。７．CPUクロック：240MHz（312Mは省略）root@x6100:~# cpufreq-set -u 240Minfocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 240 MHz and 240 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 240 MHz (asserted by call to hardware). cpufreq stats: 120 MHz:10.57%, 240 MHz:0.41%, 312 MHz:3.59%, 408 MHz:2.90%, 480 MHz:9.37%, 504 MHz:2.53%, 600 MHz:2.97%, 648 MHz:2.84%, 720 MHz:5.33%, 816 MHz:2.29%, 912 MHz:6.50%, 1.01 GHz:50.68% (15)■画面はwaterfallの描画が明らかに遅くなった。（静止画だと分からないので動画で）【まずはデフォルトの1.01GHzの場合】【240MHzの場合】８．CPUクロック：120MHzroot@x6100:~# cpufreq-set -u 120Minfocpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009Report 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: 244 us. hardware limits: 120 MHz - 1.01 GHz available frequency steps: 120 MHz, 240 MHz, 312 MHz, 408 MHz, 480 MHz, 504 MHz, 600 MHz, 648 MHz, 720 MHz, 816 MHz, 912 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 120 MHz and 120 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 120 MHz (asserted by call to hardware). cpufreq stats: 120 MHz:10.97%, 240 MHz:2.50%, 312 MHz:3.49%, 408 MHz:2.82%, 480 MHz:9.11%, 504 MHz:2.46%, 600 MHz:2.89%, 648 MHz:2.76%, 720 MHz:5.18%, 816 MHz:2.23%, 912 MHz:6.32%, 1.01 GHz:49.26% (16)■画面はwaterfallの描画が更新されなくなった（右上のAudio spectrum display は更新されている）
