From: Yixun Lan <dlan@kernel.org>
To: Dave Klotz <DaveWK225@protonmail.com>
Cc: u-boot@lists.u-boot-project.org,
Huan Zhou <pericycle.cc@gmail.com>,
Eric Chung <eric.chung@riscstar.com>,
Tom Rini <trini@konsulko.com>, Guodong Xu <docular.xu@gmail.com>,
Raymond Mao <raymond.mao@riscstar.com>,
E Shattow <e@freeshell.de>,
u-boot-spacemit@groups.io
Subject: Re: [PATCH RESEND 0/2] spacemit: k1: SPL robustness for boards without a PMIC or SPI NOR
Date: Thu, 22 Oct 2026 22:49:51 +0000 [thread overview]
Message-ID: <20261022224951-GKB125937@kernel.org> (raw)
In-Reply-To: <cover.1790976767.git.DaveWK225@protonmail.com>
Hi Dave,
On 21:32 Fri 02 Oct , Dave Klotz wrote:
> Resent: the first posting's cover letter went out with the same
> Message-ID as the cover letter of "pci: spacemit: fixes for the K1 PCIe
> host driver", so this series threaded under that one. No changes.
>
> Two small SPL changes for K1 boards that do not look like the BPI-F3
> and MusePi Pro:
>
> 1. pmic_init() and nor_early_init() panic when the device tree gives
> the SPL no PMIC or no SPI controller. A board that boots from eMMC or
> microSD with its rails already up (the OrangePi R2S and RV2) stops
> there. Log it and carry on.
> 2. Provide board_boot_order(): the device the BootROM booted from, as
> detected now, then the other MMC controller and SPI NOR, so an
> unexpected BootROM path still finds U-Boot.
>
> Tested on an OrangePi RV2 booting from microSD (no SPI controller in
> the SPL): "No SPI controller", then the SPL loads U-Boot from the card
> through the detected MMC2. The fallback order was not exercised, since
> the detection was right.
>
> Dave Klotz (2):
> spacemit: k1: do not require a PMIC or an SPI controller in SPL
> spacemit: k1: fall back to the other boot devices in SPL
>
> board/spacemit/k1/spl.c | 48 +++++++++++++++++++++++++++++++++++++----
> 1 file changed, 44 insertions(+), 4 deletions(-)
>
For the series, with
Reviewed-by: Yixun Lan <dlan@kernel.org>
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-10-22 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 21:32 [PATCH RESEND 0/2] spacemit: k1: SPL robustness for boards without a PMIC or SPI NOR Dave Klotz
2026-10-02 21:33 ` [PATCH RESEND 1/2] spacemit: k1: do not require a PMIC or an SPI controller in SPL Dave Klotz
2026-10-02 21:33 ` [PATCH RESEND 2/2] spacemit: k1: fall back to the other boot devices " Dave Klotz
2026-10-02 22:07 ` [PATCH RESEND 0/2] spacemit: k1: SPL robustness for boards without a PMIC or SPI NOR Dave Klotz
2026-10-22 22:49 ` Yixun Lan [this message]
2026-10-23 1:17 ` Yixun Lan
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=20261022224951-GKB125937@kernel.org \
--to=dlan@kernel.org \
--cc=DaveWK225@protonmail.com \
--cc=docular.xu@gmail.com \
--cc=e@freeshell.de \
--cc=eric.chung@riscstar.com \
--cc=pericycle.cc@gmail.com \
--cc=raymond.mao@riscstar.com \
--cc=trini@konsulko.com \
--cc=u-boot-spacemit@groups.io \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox