U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zixian Zeng <sycamoremoon376@gmail.com>
To: Tanmay Kathpalia <tanmay.kathpalia@altera.com>,
	Peng Fan <peng.fan@nxp.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Yixun Lan <dlan@kernel.org>, Tom Rini <trini@konsulko.com>,
	Eric Chung <eric.chung@riscstar.com>
Cc: u-boot@lists.u-boot-project.org, u-boot-spacemit@groups.io,
	Dave Klotz <DaveWK225@protonmail.com>,
	Hung-Chun Tseng <alan.tseng.cs@gmail.com>,
	Anand Moon <linux.amoon@gmail.com>,
	Raymond Mao <raymond.mao@riscstar.com>,
	Huan Zhou <pericycle.cc@gmail.com>,
	Guodong Xu <guodong@riscstar.com>,
	Leo Liang <leo.liang@sifive.com>,
	Tim Ouyang <tim609@andestech.com>, Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v3 0/4] mmc: k1: multi-block SD reads in SPL and a probe failure fix
Date: Thu, 5 Nov 2026 22:40:12 +0800	[thread overview]
Message-ID: <4b3f9200-ebbd-4e17-9205-58827c426edd@gmail.com> (raw)
In-Reply-To: <20261031215452.16013-1-tanmay.kathpalia@altera.com>

On 2026/11/1 05:54, Tanmay Kathpalia wrote:
> I am taking this series over from Dave (thanks, Dave).
> 
> Testing v2 2/3 on a Banana Pi BPI-F3 and a Milk-V Jupiter showed that
> multi-block SD reads in the SPL fail because the SD I/O rail (PMIC
> aldo1) is at 1.8 V: set_vdd_mmc() sets it, and without
> SPL_MMC_IO_VOLTAGE the MMC core never sets it back to 3.3 V. Patch 1
> lets the MMC core set the rail, patch 2 drops set_vdd_mmc(), patch 3
> is Dave's multi-block change, and patch 4 is Dave's probe error path
> fix, narrowed to the resets because, as Yixun pointed out, the clocks
> are reference counted.
> 
> Not in this version:
> - v2 1/3 (missing max-frequency). As Yixun suggested, the io clock
>    should be set up with assigned-clock-parents/rates in the DT, which
>    also works for Linux; that will follow separately. Hung-Chun has
>    withdrawn his matching RFC.
> - SPL_PINCTRL. On its own it links no K1 pinctrl driver into the SPL
>    (there is no SPL Kconfig symbol for it yet), so it would not program
>    any pads. It will follow separately once it has been tested on
>    hardware.
> 
> Testing: I do not have a K1 board, so v3 itself is build-tested only.
> The changes were tested piecewise in the v2 thread, and in each case
> multi-block SD reads in the SPL worked: Zixian enabled
> SPL_MMC_IO_VOLTAGE on a BPI-F3, Yixun dropped set_vdd_mmc() alone on
> a BPI-F3, and Hung-Chun set aldo1 to 3.3 V on a Jupiter. Zixian,
> Yixun, Hung-Chun: a Tested-by on v3 would be much appreciated.
> 
> Thanks also to Anand for testing v2.
> 
> v2: https://lore.kernel.org/u-boot/20261005T135220-0400.mmc-v2-0001.DaveWK225@protonmail.com/
> 
> Changes in v3:
> - New: configs: k1: enable SPL_MMC_IO_VOLTAGE
> - New: spacemit: k1: do not force the SD I/O rail to 1.8 V in SPL
> - v2 2/3 -> 3/4: commit message explains the BPI-F3 and Jupiter
>    failures; code unchanged
> - v2 3/3 -> 4/4: keep clk_release_bulk(), only drop
>    reset_release_bulk()
> - Drop v2 1/3
> 
> Dave Klotz (2):
>    mmc: k1: let the SPL read SD cards more than one block at a time
>    mmc: k1: do not assert the shared AXI reset on probe failure
> 
> Tanmay Kathpalia (2):
>    configs: k1: enable SPL_MMC_IO_VOLTAGE
>    spacemit: k1: do not force the SD I/O rail to 1.8 V in SPL
> 
>   arch/riscv/dts/k1-bananapi-f3-u-boot.dtsi | 10 ++++----
>   arch/riscv/dts/k1-musepi-pro-u-boot.dtsi  |  2 +-
>   board/spacemit/k1/spl.c                   | 21 -----------------
>   configs/spacemit_k1_defconfig             |  1 +
>   doc/board/spacemit/k1-spl.rst             |  1 -
>   drivers/mmc/spacemit_sdhci.c              | 28 ++++++++---------------
>   6 files changed, 17 insertions(+), 46 deletions(-)
> 

Working fine, sorry for late testing.

Tested-by: Zixian Zeng <sycamoremoon376@gmail.com> # Babanapi-F3

  parent reply	other threads:[~2026-11-05 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 21:54 [PATCH v3 0/4] mmc: k1: multi-block SD reads in SPL and a probe failure fix Tanmay Kathpalia
2026-10-31 21:54 ` [PATCH v3 1/4] configs: k1: enable SPL_MMC_IO_VOLTAGE Tanmay Kathpalia
2026-10-31 21:54 ` [PATCH v3 2/4] spacemit: k1: do not force the SD I/O rail to 1.8 V in SPL Tanmay Kathpalia
2026-10-31 21:54 ` [PATCH v3 3/4] mmc: k1: let the SPL read SD cards more than one block at a time Tanmay Kathpalia
2026-10-31 21:54 ` [PATCH v3 4/4] mmc: k1: do not assert the shared AXI reset on probe failure Tanmay Kathpalia
2026-11-05 14:08 ` [PATCH v3 0/4] mmc: k1: multi-block SD reads in SPL and a probe failure fix Yixun Lan
2026-11-05 14:40 ` Zixian Zeng [this message]
2026-11-06 20:09   ` Kathpalia, Tanmay
2026-11-05 22:27 ` Yixun Lan
2026-11-09  6:32   ` Peng Fan
2026-11-11  9:45 ` 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=4b3f9200-ebbd-4e17-9205-58827c426edd@gmail.com \
    --to=sycamoremoon376@gmail.com \
    --cc=DaveWK225@protonmail.com \
    --cc=alan.tseng.cs@gmail.com \
    --cc=dlan@kernel.org \
    --cc=eric.chung@riscstar.com \
    --cc=guodong@riscstar.com \
    --cc=jh80.chung@samsung.com \
    --cc=leo.liang@sifive.com \
    --cc=linux.amoon@gmail.com \
    --cc=me@ziyao.cc \
    --cc=peng.fan@nxp.com \
    --cc=pericycle.cc@gmail.com \
    --cc=raymond.mao@riscstar.com \
    --cc=tanmay.kathpalia@altera.com \
    --cc=tim609@andestech.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