Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Val Packett <val@packett.cool>
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 0/3] arm64: dts: qcom: sm8x50: Enable UHS-I SDR50 and SDR104 SD card modes
Date: Wed, 26 Nov 2025 13:14:53 -0300	[thread overview]
Message-ID: <bdf3f54d-a223-4eff-aa71-0d74a83ef46d@packett.cool> (raw)
In-Reply-To: <20251126012043.3764567-1-vladimir.zapolskiy@linaro.org>

Hi,

On 11/25/25 10:20 PM, Vladimir Zapolskiy wrote:
> The reported problem of some non-working UHS-I speed modes on SM8450
> originates in commit 0a631a36f724 ("arm64: dts: qcom: Add device tree
> for Sony Xperia 1 IV"), and then it was spread to all SM8450 powered
> platforms by commit 9d561dc4e5cc ("arm64: dts: qcom: sm8450: disable
> SDHCI SDR104/SDR50 on all boards").
>
> The tests show that the rootcause of the problem was related to an
> overclocking of SD cards, and it's fixed later on by commit a27ac3806b0a
> ("clk: qcom: gcc-sm8450: Use floor ops for SDCC RCGs").
>
> Due to a missed setting of an appropriate SDCC clock operations in
> platform GCC driver the workaround of dropping SD card speeds from UHS-I
> to high speed was spread to SM8550 and SM8650 platforms, and since
> the fixes in the clock controller drivers are ready [1], it should be
> safe to remove the speed mode restrictions from SM8450, SM8550 and
> SM8650 platforms.
> [..]

I see you have tested with dd on the raw block device, but have you 
tested hotplugging SD cards that have partition tables and filesystems 
on them?

We have this kind of issue on Hamoa where we get I/O errors early, right 
after the card is inserted and the partition table / filesystem headers 
are being read:

[  714.057106] mmc0: new UHS-I speed SDR104 SDXC card at address 0001
[  714.060567] mmcblk0: mmc0:0001 EC2QT 59.6 GiB
[  714.503873] I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 
phys_seg 1 prio class 2
[  714.505660] Buffer I/O error on dev mmcblk0, logical block 0, async 
page read
[  714.513632] I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 
phys_seg 1 prio class 2
[  714.516469] Buffer I/O error on dev mmcblk0, logical block 0, async 
page read
[  714.516512]  mmcblk0: unable to read partition table

and b1f856b1727c ("mmc: sdhci-msm: Avoid early clock doubling during 
HS400 transition") did not help..


~val


  parent reply	other threads:[~2025-11-26 16:15 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
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 ` Val Packett [this message]
2025-11-26 17:17   ` [PATCH 0/3] arm64: dts: qcom: sm8x50: " 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=bdf3f54d-a223-4eff-aa71-0d74a83ef46d@packett.cool \
    --to=val@packett.cool \
    --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