From: Yixun Lan <dlan@kernel.org>
To: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
Cc: Eric Chung <eric.chung@riscstar.com>,
Huan Zhou <pericycle.cc@gmail.com>, Peng Fan <peng.fan@nxp.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
E Shattow <e@freeshell.de>, Guodong Xu <guodong@riscstar.com>,
Raymond Mao <raymond.mao@riscstar.com>,
u-boot-spacemit@groups.io, u-boot@lists.u-boot-project.org
Subject: Re: [RFC PATCH 0/2] mmc: k1: do not require max-frequency in the device tree
Date: Tue, 13 Oct 2026 08:56:54 +0000 [thread overview]
Message-ID: <20261013085654-GKA65630@kernel.org> (raw)
In-Reply-To: <20261013084448.433298-1-alan.tseng.cs@gmail.com>
Hi Hung-Chun,
On 16:44 Tue 13 Oct , Hung-Chun Tseng wrote:
> The K1 SDHCI driver sets the io clock to cfg.f_max, which is only
> filled in from a "max-frequency" property, so each K1 board carries
> max-frequency = <204800000> for the SD and eMMC nodes in its
> -u-boot.dtsi. E Shattow pointed out that this property is unlikely to
> be accepted in the upstream device tree and looks like a driver issue
> [1]. The Linux driver indeed does not need it: it reports the current
> io clock rate as the maximum.
>
> Patch 1 makes the U-Boot driver do the same when max-frequency is
> absent. Patch 2 drops the property from the BPI-F3 and MusePi Pro
> overlays.
>
> This is an RFC because I could only build-test it: spacemit_k1_defconfig
> builds (SPL and u-boot.itb), and the resulting BPI-F3 and MusePi Pro
> DTBs no longer carry max-frequency on the MMC nodes. I have not run it
> on hardware. The open question is what rate the io clock runs at when
> SPL and U-Boot probe the controllers: if the BootROM or SPL leaves it
> well below 204.8 MHz, SD and eMMC will still work but run slower, and
> the driver may need a default rate instead of the current one. A test
> on a BPI-F3 or MusePi Pro, or a pointer to the expected clock setup,
> would be very welcome.
>
> [1] https://lore.kernel.org/u-boot/5d323a11-da4e-4071-bdeb-ab5c03e8f85e@freeshell.de/
>
Please do not start a new thread, as there is already one discussion, see
https://lore.kernel.org/all/20261005T135220-0400.mmc-v2-0001.DaveWK225@protonmail.com/
> Hung-Chun Tseng (2):
> mmc: k1: use the io clock rate when max-frequency is absent
> riscv: dts: k1: drop max-frequency from the SD and eMMC nodes
>
> arch/riscv/dts/k1-bananapi-f3-u-boot.dtsi | 2 --
> arch/riscv/dts/k1-musepi-pro-u-boot.dtsi | 2 --
> drivers/mmc/spacemit_sdhci.c | 24 +++++++++++++++++++----
> 3 files changed, 20 insertions(+), 8 deletions(-)
>
> --
> 2.43.0
>
--
Yixun Lan (dlan)
prev parent reply other threads:[~2026-10-13 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 8:44 [RFC PATCH 0/2] mmc: k1: do not require max-frequency in the device tree Hung-Chun Tseng
2026-10-13 8:44 ` [RFC PATCH 1/2] mmc: k1: use the io clock rate when max-frequency is absent Hung-Chun Tseng
2026-10-14 12:15 ` Tanmay Kathpalia
2026-10-13 8:44 ` [RFC PATCH 2/2] riscv: dts: k1: drop max-frequency from the SD and eMMC nodes Hung-Chun Tseng
2026-10-13 8:56 ` Yixun Lan [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=20261013085654-GKA65630@kernel.org \
--to=dlan@kernel.org \
--cc=alan.tseng.cs@gmail.com \
--cc=e@freeshell.de \
--cc=eric.chung@riscstar.com \
--cc=guodong@riscstar.com \
--cc=jh80.chung@samsung.com \
--cc=peng.fan@nxp.com \
--cc=pericycle.cc@gmail.com \
--cc=raymond.mao@riscstar.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