| author | Minas Hambardzumyan <minas@ti.com> | |
| Tue, 22 Mar 2022 11:27:12 +0000 (06:27 -0500) | ||
| committer | Minas Hambardzumyan <minas@ti.com> | |
| Fri, 8 Apr 2022 15:42:15 +0000 (10:42 -0500) | ||
| commit | fefaf9bdd6f36ab0cebaab8dbf34e5beb50f471c | |
| tree | 9c5b698bf53b0ae608d80098995935c8395f7fa7 | tree | snapshot (tar.xz tar.gz zip) |
| parent | a3126fd88edd911fff33ace5b813652397bf4cfe | commit | diff |
scripts/runDhrystone: set the frequency for k3 devices
Current implementation of the runDhrystone script relies on
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq file to get the
core frequency. This gives a frequency of 400MHz for most TI processors,
which is not the correct value. As a result, the benchmark
calculates/reports an incorrect value for DMIPS/MHz.
This update relies on `k3conf` program to get the correct frequency for
TI K3 platforms. Implemented logic relies on the frequency reported for
the first core and assumes all cores are operating at the same frequency.
Signed-off-by: Minas Hambardzumyan <minas@ti.com>
Current implementation of the runDhrystone script relies on
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq file to get the
core frequency. This gives a frequency of 400MHz for most TI processors,
which is not the correct value. As a result, the benchmark
calculates/reports an incorrect value for DMIPS/MHz.
This update relies on `k3conf` program to get the correct frequency for
TI K3 platforms. Implemented logic relies on the frequency reported for
the first core and assumes all cores are operating at the same frequency.
Signed-off-by: Minas Hambardzumyan <minas@ti.com>
| scripts/runDhrystone | diff | blob | history |