From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm8550: Enable UHS-I SDR50 and SDR104 SD card modes
Date: Thu, 27 Nov 2025 14:40:28 +0100 [thread overview]
Message-ID: <b07b88ed-83a3-46d6-8b97-e8661e2cfaa3@oss.qualcomm.com> (raw)
In-Reply-To: <20251126012043.3764567-3-vladimir.zapolskiy@linaro.org>
On 11/26/25 2:20 AM, Vladimir Zapolskiy wrote:
> The restriction on UHS-I speed modes was added to all SM8550 platforms
> by copying it from SM8450 dtsi file, and due to the overclocking of SD
> cards it was an actually reproducible problem. Since the latter issue
> has been fixed, UHS-I speed modes are working fine on SM8550 boards,
> below is the test performed on SM8550-HDK:
>
> SDR50 speed mode:
>
> mmc0: new UHS-I speed SDR50 SDHC card at address 0001
> mmcblk0: mmc0:0001 00000 14.6 GiB
> mmcblk0: p1
>
> % dd if=/dev/mmcblk0p1 of=/dev/null bs=1M count=1024
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 23.5468 s, 45.6 MB/s
>
> SDR104 speed mode:
>
> mmc0: new UHS-I speed SDR104 SDHC card at address 59b4
> mmcblk0: mmc0:59b4 USDU1 28.3 GiB
> mmcblk0: p1
>
> % dd if=/dev/mmcblk0p1 of=/dev/null bs=1M count=1024
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 11.9819 s, 89.6 MB/s
>
> Unset the UHS-I speed mode restrictions from the SM8550 platform dtsi
> file, there is no indication that the SDHC controller is broken.
>
> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> ---
8550 has additional limitations. One was addressed recently with
max-sd-hs-hz (HS mode can only run at 37.5 MHz), but when in SDR104,
the frequency must also be capped to 148 MHz. I don't know whether
the driver respects that today.
Konrad
next prev parent reply other threads:[~2025-11-27 13:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 1:20 [PATCH 0/3] arm64: dts: qcom: sm8x50: Enable UHS-I SDR50 and SDR104 SD card modes Vladimir Zapolskiy
2025-11-26 1:20 ` [PATCH 1/3] arm64: dts: qcom: sm8450: " Vladimir Zapolskiy
2025-11-26 8:09 ` Neil Armstrong
2025-11-27 13:43 ` Konrad Dybcio
2025-11-26 1:20 ` [PATCH 2/3] arm64: dts: qcom: sm8550: " Vladimir Zapolskiy
2025-11-26 8:08 ` Neil Armstrong
2025-11-27 13:40 ` Konrad Dybcio [this message]
2025-11-27 14:27 ` Vladimir Zapolskiy
2025-11-28 11:04 ` Konrad Dybcio
2025-11-26 1:20 ` [PATCH 3/3] arm64: dts: qcom: sm8650: " Vladimir Zapolskiy
2025-11-26 8:08 ` Neil Armstrong
2025-11-27 13:42 ` Konrad Dybcio
2025-11-26 16:14 ` [PATCH 0/3] arm64: dts: qcom: sm8x50: " Val Packett
2025-11-26 17:17 ` Vladimir Zapolskiy
2025-11-27 13:47 ` Konrad Dybcio
2025-11-27 19:33 ` Val Packett
2025-11-28 1:19 ` Vladimir Zapolskiy
2025-11-28 9:46 ` Konrad Dybcio
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=b07b88ed-83a3-46d6-8b97-e8661e2cfaa3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vladimir.zapolskiy@linaro.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