From: William Bright <william.bright@imd-tec.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
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, 9 Jun 2026 17:21:42 +0100 [thread overview]
Message-ID: <aig9licCxhtZbHMq@will-Legion-Slim-5-16APH8> (raw)
In-Reply-To: <e0731edc-81da-429a-a12e-a1d1b75f9544@linaro.org>
On Thu, Jun 04, 2026 at 07:01:22PM +0300, Vladimir Zapolskiy wrote:
>
> How do you know that these modes are broken in hardware and not
> caused by something else?
>
> It was stated before, but it was proven to be invalid as the statement.
>
Thanks Vladimir for your feedback.
I copied this statement from when these modes were also masked out on
sdhc_2. I see that there was progress since then and the caps mask has
been dropped so I agree that I shouldn't have this comment that these
modes are broken due to hardware.
I have tested this patch after rebasing onto the latest tree with the
recent changes that allowed for the caps mask to be dropped for sdhc_2
and I still see dll tuning failing. To progress, I need some guidance
from qcom as to what dll-config value should be used as I am uncertain
about this. I noticed that ftbl_gcc_sdcc4_apps_clk_src only goes up to
75MHz so perhaps this needs modifying for DLL-tuning to pass and maybe
there needs to be schematic/routing guidance that needs to be strictly
followed as-well besides the usual 50 ohm impedance rules?
> > - Forbid SDR104/SDR50 via sdhci-caps-mask, matching the previously
> > existing sdhc_2 workaround in the same file.
> > The SDHCI capabilities register on this SoC advertises SDR50/SDR104
> > modes that are broken on sdhc_4; without masking them the MMC
> > core selects SDR50 and fails DLL tuning with
> > -ETIMEDOUT during SDIO card initialisation.
>
> Which one SDIO card do you test?
>
My apologies, I made a mistake in the cover letter, I wasn't testing with
an SDIO card, I was testing with an NXP IW416 which is hard-wired to
sdhc_4.
Best regards,
Will
next prev parent reply other threads:[~2026-06-09 16:21 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 [this message]
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
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=aig9licCxhtZbHMq@will-Legion-Slim-5-16APH8 \
--to=william.bright@imd-tec.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=linux-kernel@vger.kernel.org \
--cc=ram@imd-tec.com \
--cc=robh@kernel.org \
--cc=tendai.makumire@imd-tec.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