Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
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,
	Sarthak Garg <sarthak.garg@oss.qualcomm.com>
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm8550: Enable UHS-I SDR50 and SDR104 SD card modes
Date: Fri, 28 Nov 2025 12:04:13 +0100	[thread overview]
Message-ID: <d4f58ebd-631f-4ccd-a36b-ac562be7bc68@oss.qualcomm.com> (raw)
In-Reply-To: <d3cccdf4-8c50-4b6c-a29b-5b1388ce2249@linaro.org>

On 11/27/25 3:27 PM, Vladimir Zapolskiy wrote:
> Hi Konrad.
> 
> On 11/27/25 15:40, Konrad Dybcio wrote:
>> 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.
>>
> 
> This frequency cap tuning for SDR104 speed mode is not done. If I
> remember the story properly, the frequency cap for HS speed mode was
> implemented in dts instead of being a pure Qualcomm SDHC specific
> quirk, because it's possible to workaround the limitation by slightly
> changing a board PCB layout. Then should this new SDR104 quirk be
> considered due to a property in the dtb as well?

I think so.

> FWIW, comparing register dumps SD host controllers on SM8550 and SM8650
> SoCs are identical, should HS and SDR104 quirks be ported to SM8650 also?

A document says that in 8650 and 8750 (and hamoa) and newer, these issues
are not present, however the original author added the same limitation to
sm8750:

https://lore.kernel.org/linux-arm-msm/20251026111746.3195861-3-sarthak.garg@oss.qualcomm.com/

+Sarthak could you please remind us why it'd be necessary on !8550?

Konrad

  reply	other threads:[~2025-11-28 11:04 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
2025-11-27 14:27     ` Vladimir Zapolskiy
2025-11-28 11:04       ` Konrad Dybcio [this message]
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=d4f58ebd-631f-4ccd-a36b-ac562be7bc68@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=sarthak.garg@oss.qualcomm.com \
    --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