Jump to content

[Armbian build PR] - arm64-dts-allwinner-h616-Add-efuse_xlate-cpu-frequency-scaling-v1_6_2


Recommended Posts

Posted

Description

Add cpu-frequency to orangepizero2, allwinner h616 6.x.y kernels

Follow up Jira reference number AR-1683

How Has This Been Tested?

Armbian 23.05.0-trunk Bullseye ttyS0

orangepizero2 login: alistair
Password:
  ___  ____  _   _____             ____
 / _ \|  _ \(_) |__  /___ _ __ ___|___ \
| | | | |_) | |   / // _ \ '__/ _ \ __) |
| |_| |  __/| |  / /|  __/ | | (_) / __/
 \___/|_|   |_| /____\___|_|  \___/_____|

Welcome to Armbian 23.05.0-trunk Bullseye with bleeding edge Linux 6.2.16-sunxi64

No end-user support: built from trunk

System load:   13%              Up time:       0 min
Memory usage:  8% of 984M       IP:            10.0.0.12
CPU temp:      42°C             Usage of /:    5% of 29G

[ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ]

alistair@orangepizero2:~$ dmesg | grep cpu*
[    0.000000] percpu: Embedded 19 pages/cpu s38760 r8192 d30872 u77824
[    0.000000] pcpu-alloc: s38760 r8192 d30872 u77824 alloc=19*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] printk: log_buf_len individual max cpu contribution: 4096 bytes
[    0.000000] printk: log_buf_len total cpu_extra contributions: 12288 bytes
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.041807] cpuidle: using governor menu
[    0.062518] cryptd: max_cpu_qlen set to 1000
[    0.700973] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.875685] ledtrig-cpu: registered to indicate activity on CPUs
[    2.053265] sun50i_cpufreq_nvmem: Using CPU speed bin speed0
[    8.995945] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 408000 KHz, changing to: 480000 KHz

  • [x] Test A BUILD compiled and booted

Checklist:

  • [x] My code follows the style guidelines of this project
  • [x] I have performed a self-review of my own code
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [x] My changes generate no new warnings
  • [x] Any dependent changes have been merged and published in downstream modules

View the full article

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines