From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
William Bright <william.bright@imd-tec.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Ram Boukobza <ram@imd-tec.com>,
Tendai Makumire <tendai.makumire@imd-tec.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: sm8550: add SDHC4 controller node
Date: Tue, 30 Jun 2026 15:41:36 +0300 [thread overview]
Message-ID: <fd78f8e8-07c6-490b-a9bd-d581a28c1f04@linaro.org> (raw)
In-Reply-To: <c9f7b597-f083-4438-bf9b-a19e2f39436a@oss.qualcomm.com>
On 6/30/26 14:09, Konrad Dybcio wrote:
> On 6/12/26 11:11 AM, Vladimir Zapolskiy wrote:
>> On 6/12/26 11:47, William Bright wrote:
>>> On Thu, Jun 11, 2026 at 10:48:34AM +0300, Vladimir Zapolskiy wrote:
>>>> Looks like the SDHC driver behaves expectedly then. For me it's hard to say
>>>> what may be the rootcause, I believe the lower bus frequency should be fine,
>>>> so it sounds like a hardware issue, but could it be PCB/board specific one?
>>>>
>>>> If you find a chance to copy the SDHC driver (and its small dependencies)
>>>> from Android and test it on your board, and if it also fails, then it might
>>>> be well concluded that something is wrong with hardware, still it won't be
>>>> quite convincing that the SoC SDHC is to blame here.
>>>>
>>>> Hope it helps.
>>>>
>>> My colleague Tendai (<tendai.makumire@imd-tec.com>) had the same issue
>>> with dll-tuning failing in SDR50 when working on the downstream 5.15 msm
>>> kernel [1].
>
> I have a "feature table" and it says SM8550->SDC4->DLL [Y/N] -> No
>
> no wonder it fails the tuning if it's not present (or that's at least
> my interpretation of this doc..)
So, is it a hardware problem of the SDHC4 controller, which reports "SDR50 mode
requires tuning" bit in CAPS1 (see SDHCI_USE_SDR50_TUNING from sdhci.h)?
https://lore.kernel.org/linux-arm-msm/aik1ZYUT-cnpfdQn@will-Legion-Slim-5-16APH8/
> There's some notes about the frequency being limited to 75 MHz in
> SDR50 and to 37.5 in DDR50.
>
> The supported modes are DS, HS, SDR12, SDR25, SDR50 and DDR50 (with
> the caveat above).
>
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2026-06-30 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 11:24 [PATCH v2] arm64: dts: qcom: sm8550: add SDHC4 controller node William Bright
2026-06-04 14:42 ` William Bright
2026-06-04 16:01 ` Vladimir Zapolskiy
2026-06-09 16:21 ` William Bright
2026-06-10 8:21 ` Vladimir Zapolskiy
2026-06-10 9:59 ` William Bright
2026-06-11 7:48 ` Vladimir Zapolskiy
2026-06-12 8:47 ` William Bright
2026-06-12 9:11 ` Vladimir Zapolskiy
2026-06-12 14:56 ` Tendai Makumire
2026-06-30 11:09 ` Konrad Dybcio
2026-06-30 12:41 ` Vladimir Zapolskiy [this message]
2026-07-01 9:16 ` 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=fd78f8e8-07c6-490b-a9bd-d581a28c1f04@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ram@imd-tec.com \
--cc=robh@kernel.org \
--cc=tendai.makumire@imd-tec.com \
--cc=william.bright@imd-tec.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