[PATCH] sunxi: Enable SPL/SPI boot for OLinuXino Lime2

[PATCH] sunxi: Enable SPL/SPI boot for OLinuXino Lime2

[Eric Anderson]

58e9502e6 "arm: sunxi: Enable SPL/SPI boot for Olinuxino Lime2-eMMC
boards" enabled SPI boot for the eMMC variant. Olimex offers the
"s16MB" variant with SPI flash populated but without eMMC populated.
Tested on board rev L.

Signed-off-by: Eric Anderson <ejona86@gmail.com>
---
 configs/A20-OLinuXino-Lime2_defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configs/A20-OLinuXino-Lime2_defconfig b/configs/A20-OLinuXino-Lime2_defconfig
index f885fc01e6e..a2c3dade795 100644
--- a/configs/A20-OLinuXino-Lime2_defconfig
+++ b/configs/A20-OLinuXino-Lime2_defconfig
@@ -2,6 +2,7 @@ CONFIG_ARM=y
 CONFIG_ARCH_SUNXI=y
 CONFIG_DEFAULT_DEVICE_TREE="sun7i-a20-olinuxino-lime2"
 CONFIG_SPL=y
+CONFIG_SPL_SPI_SUNXI=y
 CONFIG_MACH_SUN7I=y
 CONFIG_DRAM_CLK=384
 CONFIG_I2C1_ENABLE=y
-- 
2.50.0

Re: [PATCH] sunxi: Enable SPL/SPI boot for OLinuXino Lime2

[Eric Anderson]

On Mon, Aug 11, 2025 at 4:33 PM Andre Przywara <andre.przywara@arm.com> wrote:
> But actually I wonder why Olimex has two different DTs for the
> eMMC-less boards and the board with eMMC.
> ...snip...
> So I wonder if anyone wants to clean this up, because I think we would
> only need the A20-OLinuXino-Lime2-eMMC_defconfig,
> A20-OLinuXino_MICRO-eMMC_defconfig and a64-olinuxino_defconfig.

I had wondered the same, but expected I'd not understand. Looking just
now, it sounds like it doesn't mix with the NAND variant (-n8G) well?

https://github.com/torvalds/linux/commit/27dd9af6bc000ab21fdd41e58e3dddedba57ab92

It looks like the emmc DT has gotten slightly slimmer since being
introduced. It doesn't seem the eMMC DT turns off any part of the NAND
DT, so I might try to poke at this some. But I don't have a NAND
version of the board to fully test.

> >  CONFIG_SPL=y
> > +CONFIG_SPL_SPI_SUNXI=y
>
> This needs to go further down below. After configuring for a board, run
> "make savedefconfig", then compare the generated "defconfig" file
> with your ..._defconfig version (or just copy ./defconfig over).

Oh, right, the tooling would know the proper order. I just sorted it,
but I forgot I had wondered earlier how things were ordered. Thanks
for the explanation.

Thanks for fixing it up.