From: John Watts <contact@jookia.org>
To: Icenowy Zheng <uwu@icenowy.me>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Andre Przywara <andre.przywara@arm.com>,
Hans de Goede <hdegoede@redhat.com>,
Samuel Holland <samuel@sholland.org>,
Jesse Taube <mr.bossman075@gmail.com>,
u-boot@lists.denx.de, linux-sunxi@googlegroups.com
Subject: Re: [PATCH 0/8] SUNIV SPI NAND support in SPL
Date: Thu, 11 Apr 2024 14:32:51 +1000 [thread overview]
Message-ID: <Zhdn80xBMENcfnwM@titan> (raw)
In-Reply-To: <20221014030520.3067228-1-uwu@icenowy.me>
Hello,
I've used this code extensively, incorporated it in to an RFC branch of
mine during development and reviewed it in the process.
John.
Reviewed-by: John Watts <contact@jookia.org>
Tested-by: John Watts <contact@jookia.org>
On Fri, Oct 14, 2022 at 11:05:12AM +0800, Icenowy Zheng wrote:
> This patchset tries to extend SPI-based boot code in sunxi SPL to
> support SPI NAND, following the same principle with current SPI NOR code
> (mimicking the behavior of sunxi BROM). In addition, as part of test to
> this patchset, some patches for Source Parts Inc. PopStick is attached,
> although marked DO NOT MERGE because the DT should come from Linux after
> it's ready.
>
> To keep thr code that accesses SPI NAND as simple as possible, it
> assumes fixed page size, which is also what sunxi BROM does. The SUNIV
> SPL assumes 0x400 page size, but here to utilize the space better, in
> the attached example of PopStick, U-Boot main part is assumed to be
> with 0x800 page size (which is the real situation of the W25N01 flash
> used by PopStick).
>
> Icenowy Zheng (8):
> sunxi: SPL SPI: extract code for doing SPI transfer
> sunxi: SPL SPI: add support for read command with 2 byte address
> sunxi: SPL SPI: allow multiple boot attempt
> sunxi: SPL SPI: add initial support for booting from SPI NAND
> sunxi: enable support for SPI NAND booting on SUNIV
> [DO NOT MERGE] sunxi: sync DT from my tree for PopStick
> [DO NOT MERGE, DIRTY HACK] sunxi: use UBI for environement storage
> [DO NOT MERGE] sunxi: add a defconfig for PopStick
>
> arch/arm/dts/Makefile | 3 +-
> arch/arm/dts/suniv-f1c100s-licheepi-nano.dts | 16 ++
> arch/arm/dts/suniv-f1c100s.dtsi | 26 ++
> arch/arm/dts/suniv-f1c200s-popstick-v1.1.dts | 101 ++++++++
> arch/arm/mach-sunxi/Kconfig | 16 ++
> arch/arm/mach-sunxi/board.c | 4 +-
> arch/arm/mach-sunxi/spl_spi_sunxi.c | 247 ++++++++++++++-----
> board/sunxi/board.c | 1 +
> configs/popstick_defconfig | 35 +++
> 9 files changed, 377 insertions(+), 72 deletions(-)
> create mode 100644 arch/arm/dts/suniv-f1c200s-popstick-v1.1.dts
> create mode 100644 configs/popstick_defconfig
>
> --
> 2.37.1
>
prev parent reply other threads:[~2024-04-11 4:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 3:05 [PATCH 0/8] SUNIV SPI NAND support in SPL Icenowy Zheng
2022-10-14 3:05 ` [PATCH 1/8] sunxi: SPL SPI: extract code for doing SPI transfer Icenowy Zheng
2023-01-14 19:32 ` Samuel Holland
2023-12-12 18:12 ` Andre Przywara
2022-10-14 3:05 ` [PATCH 2/8] sunxi: SPL SPI: add support for read command with 2 byte address Icenowy Zheng
2023-01-14 19:35 ` Samuel Holland
2022-10-14 3:05 ` [PATCH 3/8] sunxi: SPL SPI: allow multiple boot attempt Icenowy Zheng
2023-01-14 19:56 ` Samuel Holland
2023-01-15 0:26 ` Icenowy Zheng
2022-10-14 3:05 ` [PATCH 4/8] sunxi: SPL SPI: add initial support for booting from SPI NAND Icenowy Zheng
2023-01-14 20:08 ` Samuel Holland
2022-10-14 3:05 ` [PATCH 5/8] sunxi: enable support for SPI NAND booting on SUNIV Icenowy Zheng
2023-01-14 20:18 ` Samuel Holland
2022-10-14 3:05 ` [PATCH 6/8] [DO NOT MERGE] sunxi: sync DT from my tree for PopStick Icenowy Zheng
2022-10-14 3:05 ` [PATCH 7/8] [DO NOT MERGE, DIRTY HACK] sunxi: use UBI for environement storage Icenowy Zheng
2023-01-15 17:19 ` Icenowy Zheng
2022-10-14 3:05 ` [PATCH 8/8] [DO NOT MERGE] sunxi: add a defconfig for PopStick Icenowy Zheng
2023-06-05 21:03 ` [PATCH 0/8] SUNIV SPI NAND support in SPL Sam Edwards
2023-06-06 6:39 ` Icenowy Zheng
2023-06-06 23:09 ` Sam Edwards
2023-06-17 20:59 ` Sam Edwards
2024-04-11 4:32 ` John Watts [this message]
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=Zhdn80xBMENcfnwM@titan \
--to=contact@jookia.org \
--cc=andre.przywara@arm.com \
--cc=hdegoede@redhat.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-sunxi@googlegroups.com \
--cc=mr.bossman075@gmail.com \
--cc=samuel@sholland.org \
--cc=u-boot@lists.denx.de \
--cc=uwu@icenowy.me \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox