arm64: dts: mediatek: mt8192: Fix CPUs capacity-dmips-mhz
Subsystems (2)
PATCH 1/1 arm64: dts: mediatek: mt8192: Fix CPUs capacity-dmips-mhz
The capacity-dmips-mhz parameter was miscalculated: this SoC runs the first (Cortex-A55) cluster at a maximum of 2000MHz and the second (Cortex-A76) cluster at a maximum of 2200MHz.
In order to calculate the right capacity-dmips-mhz, the following test was performed:
1. CPUFREQ governor was set to 'performance' on both clusters
2. Ran dhrystone with 500000000 iterations for 10 times on each cluster
3. Calculated the mean result for each cluster
4. Calculated DMIPS/MHz: dmips_mhz = dmips_per_second / cpu_mhz
5. Scaled results to 1024:
result_c0 = dmips_mhz_c0 / dmips_mhz_c1 * 1024
The mean results for this SoC are:
Cluster 0 (LITTLE): 12016411 Dhry/s
Cluster 1 (BIG): 31702034 Dhry/s
The calculated scaled results are:
Cluster 0: 426.953226899238 (rounded to 427)
Cluster 1: 1024
---
arch/arm64/boot/dts/mediatek/mt8192.dtsi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
arch/arm64/boot/dts/mediatek/mt8192.dtsi +4 -4
@@ -71,7 +71,7 @@ cpu0: cpu@0 { d-cache-sets = <128>; next-level-cache = <&l2_0>; performance-domains = <&performance 0>; - capacity-dmips-mhz = <530>; + capacity-dmips-mhz = <427>; }; cpu1: cpu@100 {
@@ -89,7 +89,7 @@ cpu1: cpu@100 { d-cache-sets = <128>; next-level-cache = <&l2_0>; performance-domains = <&performance 0>; - capacity-dmips-mhz = <530>; + capacity-dmips-mhz = <427>; }; cpu2: cpu@200 {
@@ -107,7 +107,7 @@ cpu2: cpu@200 { d-cache-sets = <128>; next-level-cache = <&l2_0>; performance-domains = <&performance 0>; - capacity-dmips-mhz = <530>; + capacity-dmips-mhz = <427>; }; cpu3: cpu@300 {
@@ -125,7 +125,7 @@ cpu3: cpu@300 { d-cache-sets = <128>; next-level-cache = <&l2_0>; performance-domains = <&performance 0>; - capacity-dmips-mhz = <530>; + capacity-dmips-mhz = <427>; }; cpu4: cpu@400 {
Signature · 1 line
2.40.1
Il 02/06/23 20:35, Nícolas F. R. A. Prado ha scritto:
Quoted 17 lines
The capacity-dmips-mhz parameter was miscalculated: this SoC runs the first (Cortex-A55) cluster at a maximum of 2000MHz and the second (Cortex-A76) cluster at a maximum of 2200MHz.
In order to calculate the right capacity-dmips-mhz, the following test was performed:
1. CPUFREQ governor was set to 'performance' on both clusters
2. Ran dhrystone with 500000000 iterations for 10 times on each cluster
3. Calculated the mean result for each cluster
4. Calculated DMIPS/MHz:dmips_mhz=dmips_per_second/cpu_mhz
5. Scaled results to 1024:result_c0 = dmips_mhz_c0 / dmips_mhz_c1 * 1024The mean results for this SoC are:
Cluster 0 (LITTLE): 12016411 Dhry/s
Cluster 1 (BIG): 31702034 Dhry/s
Quoted 7 lines
The calculated scaled results are:
Cluster 0: 426.953226899238 (rounded to 427)
Cluster 1: 1024Fixes 48489980e27e ("arm64: dts: Add Mediatek SoC MT8192 and evaluation board dts and Makefile")Signed-off-by Nícolas F. R. A. Prado <[email protected]>
Quoted 26 lines · AngeloGioacchino Del Regno
Il 02/06/23 20:35, Nícolas F. R. A. Prado ha scritto:
Quoted 24 lines
The capacity-dmips-mhz parameter was miscalculated: this SoC runs the first (Cortex-A55) cluster at a maximum of 2000MHz and the second (Cortex-A76) cluster at a maximum of 2200MHz.
In order to calculate the right capacity-dmips-mhz, the following test was performed:
1. CPUFREQ governor was set to 'performance' on both clusters
2. Ran dhrystone with 500000000 iterations for 10 times on each cluster
3. Calculated the mean result for each cluster
4. Calculated DMIPS/MHz:dmips_mhz=dmips_per_second/cpu_mhz
5. Scaled results to 1024:
result_c0=dmips_mhz_c0/dmips_mhz_c1* 1024The mean results for this SoC are:
Cluster 0 (LITTLE): 12016411 Dhry/s
Cluster 1 (BIG): 31702034 Dhry/sThe calculated scaled results are:
Cluster 0: 426.953226899238 (rounded to 427)
Cluster 1: 1024Fixes 48489980e27e ("arm64: dts: Add Mediatek SoC MT8192 and evaluation board dts and Makefile")Signed-off-by Nícolas F. R. A. Prado <[email protected]>
Applied, thanks
Quoted 3 lines
Reviewed-by AngeloGioacchino Del Regno <[email protected]>
Quoted 25 lines · Matthias Brugger
Quoted 22 lines · AngeloGioacchino Del Regno
Il 02/06/23 20:35, Nícolas F. R. A. Prado ha scritto:
Quoted 21 lines
The capacity-dmips-mhz parameter was miscalculated: this SoC runs the first (Cortex-A55) cluster at a maximum of 2000MHz and the second (Cortex-A76) cluster at a maximum of 2200MHz.
In order to calculate the right capacity-dmips-mhz, the following test was performed:
1. CPUFREQ governor was set to 'performance' on both clusters
2. Ran dhrystone with 500000000 iterations for 10 times on each cluster
3. Calculated the mean result for each cluster
4. Calculated DMIPS/MHz:dmips_mhz=dmips_per_second/cpu_mhz
5. Scaled results to 1024:
result_c0=dmips_mhz_c0/dmips_mhz_c1* 1024The mean results for this SoC are:
Cluster 0 (LITTLE): 12016411 Dhry/s
Cluster 1 (BIG): 31702034 Dhry/sThe calculated scaled results are:
Cluster 0: 426.953226899238 (rounded to 427)
Cluster 1: 1024
Quoted 7 lines
Quoted 5 lines
Quoted 4 lines
Fixes 48489980e27e ("arm64: dts: Add Mediatek SoC MT8192 andevaluation board dts and
Makefile")Signed-off-by Nícolas F. R. A. Prado <[email protected]>Applied, thanks
Hi Matthias,
this patch doesn't show in your v6.4-next/dts64 branch, while the other patch you just applied does, so I just wanted to double check it was really applied.
Thanks,
Nícolas
Matthias Brugger
maintainerQuoted 32 lines · Nícolas F. R. A. Prado
Quoted 31 lines · Matthias Brugger
Quoted 27 lines · AngeloGioacchino Del Regno
Il 02/06/23 20:35, Nícolas F. R. A. Prado ha scritto:
Quoted 25 lines
The capacity-dmips-mhz parameter was miscalculated: this SoC runs the first (Cortex-A55) cluster at a maximum of 2000MHz and the second (Cortex-A76) cluster at a maximum of 2200MHz.
In order to calculate the right capacity-dmips-mhz, the following test was performed:
1. CPUFREQ governor was set to 'performance' on both clusters
2. Ran dhrystone with 500000000 iterations for 10 times on each cluster
3. Calculated the mean result for each cluster
4. Calculated DMIPS/MHz:dmips_mhz=dmips_per_second/cpu_mhz
5. Scaled results to 1024:
result_c0=dmips_mhz_c0/dmips_mhz_c1* 1024The mean results for this SoC are:
Cluster 0 (LITTLE): 12016411 Dhry/s
Cluster 1 (BIG): 31702034 Dhry/sThe calculated scaled results are:
Cluster 0: 426.953226899238 (rounded to 427)
Cluster 1: 1024Fixes 48489980e27e ("arm64: dts: Add Mediatek SoC MT8192 andevaluation board dts and
Makefile")Signed-off-by Nícolas F. R. A. Prado <[email protected]>
Quoted 7 lines
Quoted 1 line
Applied, thanks
Hi Matthias,
this patch doesn't show in your v6.4-next/dts64 branch, while the other patch you just applied does, so I just wanted to double check it was really applied.
I forgot to push it, should be fixed now.
Regards,
Matthias