Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Results for SigmaStar SSD202D on SBC2D70 sbc #37

Closed
fifteenhex opened this issue Jan 21, 2022 · 9 comments
Closed

Results for SigmaStar SSD202D on SBC2D70 sbc #37

fifteenhex opened this issue Jan 21, 2022 · 9 comments

Comments

@fifteenhex
Copy link

| SBC2D70 (SSD202D) | 1700 MHz | 5.16 | Sid armhf | 1950 | 26240 | 33120 | 770 | 3190 | - | http://ix.io/3MZY |

@ThomasKaiser
Copy link
Owner

ThomasKaiser commented Jan 21, 2022

Hi Daniel,

curious: Willy's mhz utility and /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies show 1296 MHz while /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq claims 1700 MHz. What's correct? :)

@fifteenhex
Copy link
Author

mm not sure what is going on there.
In the opp table there is up to 1296MHz as normal modes and then some 100MHz bumps after that as turbos.
The spec'd frequency for the chip is 1200MHz but it runs fine at 1800MHz as long as the voltage is high enough.
This board crashed at 1800MHz so I took it down to 1700MHz.

mhz seems to be showing the right values when I run it manually.

root@sbc2d70:~# /usr/local/src/mhz/mhz 
count=807053 us50=24254 us250=119279 diff=95025 cpu_MHz=1698.612

Willy actually fixed the clock driver to make the frequency match mhz. ;)

@ThomasKaiser
Copy link
Owner

Can you please provide output of grep . /sys/devices/system/cpu/cpufreq/policy0/*?

@fifteenhex
Copy link
Author

root@sbc2d70:~# grep . /sys/devices/system/cpu/cpufreq/policy0/*
/sys/devices/system/cpu/cpufreq/policy0/affected_cpus:0 1
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq:599999
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq:1700000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq:240000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_transition_latency:305000
/sys/devices/system/cpu/cpufreq/policy0/related_cpus:0 1
/sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies:240000 400000 600000 800000 1008000 1080000 1188000 1296000 
/sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors:ondemand performance 
/sys/devices/system/cpu/cpufreq/policy0/scaling_boost_frequencies:1350000 1404000 1458000 1512000 1600000 1700000 
/sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq:599999
/sys/devices/system/cpu/cpufreq/policy0/scaling_driver:cpufreq-dt
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:ondemand
/sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq:1700000
/sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq:240000
/sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed:<unsupported>
root@sbc2d70:~# 

@ThomasKaiser
Copy link
Owner

Alright, handling of scaling_boost_frequencies is entirely missing. I'm going to prepare a v0.9.2 soon but right now enjoying the good weather for the next hours...

Ah, which .dts are you currently using (just to to check OPP nodes there and get a better understanding of what I'm doing)?

@fifteenhex
Copy link
Author

.dts is on the top of this .dtsi with the opp stuff: https://github.com/linux-chenxing/linux/blob/mstar_v5_17_rebase/arch/arm/boot/dts/mstar-infinity2m.dtsi

Currently running with the 1800MHz frequency commented out.

@ThomasKaiser
Copy link
Owner

Could you give v0.9.2 a try please?

Would be great if you could also test a quick sbc-bench -m on bigboy too with the new version since I hope I got identifying CN8890 right (cluster/NUMA detection still broken though).

@fifteenhex
Copy link
Author

Running now..

@fifteenhex
Copy link
Author

| SBC2D70 (SSD202D) | 1700 MHz | 5.16 | Sid armhf | 1960 | 26240 | 33120 | 770 | 3190 | - | http://ix.io/3N1U |

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants