From: Danil Bezborodov <xanmilanto@gmail.com>
To: u-boot@lists.u-boot-project.org
Cc: Andre Przywara <andre.przywara@arm.com>,
Icenowy Zheng <icenowy@aosc.xyz>, Tom Rini <trini@konsulko.com>,
Danil Bezborodov <xanmilanto@gmail.com>
Subject: [PATCH] sunxi: orangepi_zero: reduce DRAM clock to 408 MHz
Date: Sun, 6 Sep 2026 00:17:57 +0300 [thread overview]
Message-ID: <20260905211757.60253-1-xanmilanto@gmail.com> (raw)
The Orange Pi Zero uses a single DDR3 chip on a 16-bit bus, unlike
the Orange Pi PC family (two chips, 32-bit) whose values this
defconfig inherited. The 624 MHz clock was never validated on this
board: commit 8792a64d8770 ("sunxi: reduce Orange Pi Zero DRAM clock
speed") lowered 672 to 624 based on lima-memtester results from an
Orange Pi PC and the PC's value in the vendor U-Boot fork.
The vendor BSP configuration for this exact board
(orangepi-xunlong/external, sys_config_orangepi_zero.fex) sets
dram_clk = 408, and Armbian has shipped a 624->408 patch for this
board - and only this board among H3 Orange Pis - since 2017.
On a 512 MB H3 variant of the board, 624 MHz produces reproducible
memory corruption caught by the kernel's early_memtest; 408 MHz
matches the vendor and Armbian values.
Signed-off-by: Danil Bezborodov <xanmilanto@gmail.com>
---
configs/orangepi_zero_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/orangepi_zero_defconfig b/configs/orangepi_zero_defconfig
index 49a1f4d0..09ce3a95 100644
--- a/configs/orangepi_zero_defconfig
+++ b/configs/orangepi_zero_defconfig
@@ -1,7 +1,7 @@
CONFIG_ARM=y
CONFIG_ARCH_SUNXI=y
CONFIG_DEFAULT_DEVICE_TREE="sun8i-h2-plus-orangepi-zero"
-CONFIG_DRAM_CLK=624
+CONFIG_DRAM_CLK=408
CONFIG_SPL=y
CONFIG_MACH_SUN8I_H3=y
# CONFIG_VIDEO_DE2 is not set
--
2.50.1 (Apple Git-155)
reply other threads:[~2026-09-06 7:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260905211757.60253-1-xanmilanto@gmail.com \
--to=xanmilanto@gmail.com \
--cc=andre.przywara@arm.com \
--cc=icenowy@aosc.xyz \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.