From: Brian Sune <briansune@gmail.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: u-boot@lists.denx.de, Dragan Simic <dsimic@manjaro.org>,
Dang Huynh <danct12@riseup.net>, Brian Sune <briansune@gmail.com>
Subject: Re: [PATCH] rockchip: remove regulator enable from device probe
Date: Sun, 2 Nov 2025 19:31:22 +0800 [thread overview]
Message-ID: <20251102113122.1038-1-briansune@gmail.com> (raw)
In-Reply-To: <20251101203429.1603832-1-jonas@kwiboo.se>
Hi Jonas,
This patch resolves the previous boot issue mentioned earlier on the mailing list:
[DEBUG] rk3399-nanopi-neo4: SPL SD init may report -5 due to SD power-on timing
Quoting the earlier observation:
"
While testing mainline U-Boot (v2026.01-rc1-00070-ge34d01d23e45) on the
FriendlyARM NanoPi NEO4 (RK3399), I observed that SPL sometimes fails to
initialize the SD card with the following message:
spl: mmc init failed with error: -5
SPL: failed to boot from all boot devices
"
So the NanoPi NEO4 boot stall appears to have been caused by the previous regulator patch.
However, it is puzzling why the issue only affected SD boot and not MMC.
This suggests that the delay method proposed earlier regarding power-on timing
is not the actual root cause of the RK3399 NanoPi NEO4 SD boot stall.
Tested with this patch applied, and SD boot now works normally.
Regards,
Brian
next prev parent reply other threads:[~2025-11-02 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 20:34 [PATCH] Revert "power: regulator: Add vin-supply for GPIO and Fixed regulators" Jonas Karlman
2025-11-01 21:15 ` Dragan Simic
2025-11-01 21:17 ` Mark Kettenis
2025-11-01 21:23 ` Dragan Simic
2025-11-02 2:00 ` Jonas Karlman
2025-11-02 7:54 ` Dragan Simic
2025-11-02 11:31 ` Brian Sune [this message]
2025-11-03 11:42 ` [PATCH] rockchip: remove regulator enable from device probe Sune Brian
2025-11-03 8:51 ` [PATCH] Revert "power: regulator: Add vin-supply for GPIO and Fixed regulators" Peng Fan
2025-11-03 10:36 ` Jonas Karlman
2025-11-03 11:03 ` Quentin Schulz
2025-11-07 7:31 ` Ye Li
2025-11-07 14:25 ` Jonas Karlman
2025-11-06 16:59 ` Tom Rini
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=20251102113122.1038-1-briansune@gmail.com \
--to=briansune@gmail.com \
--cc=danct12@riseup.net \
--cc=dsimic@manjaro.org \
--cc=jonas@kwiboo.se \
--cc=u-boot@lists.denx.de \
/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