From: "Heiko Stübner" <heiko@sntech.de>
To: Yaozhong Li <yaozhonguwl@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Yaozhong Li <yaozhonguwl@gmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: enable SD UHS-I on Firefly-RK3399
Date: Mon, 02 Nov 2026 15:02:08 +0100 [thread overview]
Message-ID: <11288903.zapYfy813O@diego> (raw)
In-Reply-To: <20261101154407.3949-1-yaozhonguwl@gmail.com>
Hi,
Am Sonntag, 1. November 2026, 16:44:07 Mitteleuropäische Normalzeit schrieb Yaozhong Li:
> Hi Heiko,
>
> Gentle ping on this one. It still applies cleanly to current mainline.
> Please let me know if you would like anything changed.
to change would be the the commit message, it is way too verbose and
quite confusing.
Also as can be seen in wifi-module datasheets, they seem to call their
main supply " VBAT - Main power voltage source input", which is
vcc3v3_sys on the firefly, so the sdio block should get an appropriate
vmmc-supply too.
The gist for a commit message as I currently get it would be like:
======
Contrary to the naming, vcc-sdio is actually the io-supply routed to the
sdmmc controller - as can be seen in the schematics.
The schematics also show the wifi block's VBAT main input source coming
from VCC3V3_SYS and it's io-supply is the already correct vcc_1v8_s3
although the datesheet is mixing namings up a bit.
Adapt the supplies for sdmmc0 and sdio accordingly and enable the sdr104
UHS mode that now becomes possible
With UHS enabled sequential read goes from 22 MB/s to 60 MB/s with a
64GB SDXC card. WiFi remained associated at 5 GHz, -50 dBm, with no
kernel errors.
======
includes adding the correct sdio vmmc-supply.
Heiko
next prev parent reply other threads:[~2026-11-02 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 5:50 [PATCH] arm64: dts: rockchip: enable SD UHS-I on Firefly-RK3399 Yaozhong Li
2026-11-01 15:44 ` Yaozhong Li
2026-11-02 14:02 ` Heiko Stübner [this message]
2026-11-01 16:10 ` Shawn Lin
2026-11-01 17:55 ` Heiko Stuebner
2026-11-02 1:06 ` Shawn Lin
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=11288903.zapYfy813O@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=yaozhonguwl@gmail.com \
/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