Linux 6.2 fails to reboot with current u-boot-nezha
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
u-boot-nezha (Ubuntu) |
Triaged
|
Wishlist
|
Heinrich Schuchardt |
Bug Description
Emil Renner Berthing reported that with Linux 6.2 he has to disabled the cpufreq_dt module to reboot when booted from u-boot-
"About cpufreq_dt on the Lichee RV: I think there might be something wrong with the latest Lichee RV u-boot from Lunar. On my Lichee RV Dock with that I get this:
root@lichee~# cat /sys/kernel/
408000000
But on my Nezha board with the older u-boot (in 2 parts with spl and toc1) I get this:
root@nezha~# cat /sys/kernel/
1008000000
Now I just changed the device tree on my Nezha sd-card, moved it to the Lichee RV Dock and booted it there, and I get 1008MHz on the Lichee RV (and cpufreq_dt works).
The "riscv" clock is the main clock for the risc-v core."
The seems to be related to the following change in upstream:
https:/
git diff smauel-
- // FIXME: no riscv architecture support for cpufreq
- cpu_opp_table: cpu-opp-table {
- compatible = "allwinner,
- "allwinner,
- nvmem-cells = <&cpu_speed_grade>;
-
- opp-1080000000 {
- // FIXME: this is probably wrong now.
- clock-latency-ns = <244144>; /* 8 32k periods */
- opp-hz = /bits/ 64 <1008000000>;
-
- // FIXME: derive a real voltage range.
- opp-microvolt-
- };
- };
Changed in u-boot-nezha (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
The 40800000 operating point was introduced in Linux v6.3 with commit
077e5f4f5528 ("riscv: dts: allwinner: Add the D1/D1s SoC devicetree")