From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Sarthak Garg <quic_sartgarg@quicinc.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
quic_nguyenb@quicinc.com, quic_rampraka@quicinc.com,
quic_pragalla@quicinc.com, quic_sayalil@quicinc.com,
quic_nitirawa@quicinc.com, quic_bhaskarv@quicinc.com,
kernel@oss.qualcomm.com
Subject: Re: [PATCH V5 4/4] arm64: dts: qcom: sm8550: Add max-sd-hs-hz property
Date: Thu, 4 Sep 2025 12:51:45 +0200 [thread overview]
Message-ID: <23c29fb7-c0a4-4519-9b8d-e68255b83a10@kernel.org> (raw)
In-Reply-To: <be87fb2f-7036-4039-8ba2-63d54a9ae732@oss.qualcomm.com>
On 04/09/2025 10:36, Konrad Dybcio wrote:
> On 9/3/25 10:21 AM, 'Krzysztof Kozlowski' via kernel wrote:
>> On 03/09/2025 10:04, Sarthak Garg wrote:
>>> Due to board-specific hardware constraints particularly related
>>> to level shifter in this case the maximum frequency for SD High-Speed
>>> (HS) mode must be limited to 37.5 MHz to ensure reliable operation of SD
>>> card in HS mode.
>>>
>>> This is achieved by introducing the `max-sd-hs-hz` property in the
>>> device tree, allowing the controller to operate within safe frequency
>>> limits for HS mode.
>>>
>>
>> Probably we will now replicate the same discussion... And it will be
>> happening every time you send the same and not reflect it in commit msg.
>>
>> Bindings say board setup, this commit msg says board config, but the
>> patch says SoC. This is not correct.
>
> Both are correct, looking at the problem from two perspectives.
>
> The bindings description mentions board-specific limitations (e.g. because
> "the board's electrical design does not allow one to achieve the full rated
> frequency that the SoC can otherwise do, in a stable way")
>
> Here the author tries to argue that almost all SM8550 boards are broken
> in this sense, because the reference design did not feature the required
> passive components, making most (derivative) designs sort of "broken by
> default" - and only some (if any?) vendors decided to go with the
> additional components required to lift this limitation.
>
> This in turn makes it fair to assume the developer experience would benefit
> from having the SD card high speed modes always work (with the slight speed
> cap which may not be required for the 1 or 2 designs that took the extra
> step) without each board DT creator having to track down this property
> separately.
And then if you send same v3, I will ask the same. Can the author
finally write commit msgs reflecting discussions and previous disagreements?
Reviewers questions happen for a reason, so sending the same means
person ignored that reason.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-04 10:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 8:04 [PATCH V5 0/4] Add level shifter support for qualcomm SOC's Sarthak Garg
2025-09-03 8:04 ` [PATCH V5 1/4] mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card Sarthak Garg
2025-09-03 8:04 ` [PATCH V5 2/4] dt-bindings: mmc: controller: Add max-sd-hs-frequency property Sarthak Garg
2025-09-03 8:22 ` Krzysztof Kozlowski
2025-09-04 8:07 ` Sarthak Garg
2025-09-03 20:39 ` Rob Herring
2025-09-04 8:15 ` Sarthak Garg
2025-09-03 8:04 ` [PATCH V5 3/4] mmc: core: Introduce a new flag max-sd-hs-hz Sarthak Garg
2025-09-03 8:04 ` [PATCH V5 4/4] arm64: dts: qcom: sm8550: Add max-sd-hs-hz property Sarthak Garg
2025-09-03 8:21 ` Krzysztof Kozlowski
2025-09-04 8:36 ` Konrad Dybcio
2025-09-04 10:51 ` Krzysztof Kozlowski [this message]
2025-09-04 10:52 ` Krzysztof Kozlowski
2025-09-04 12:27 ` Konrad Dybcio
2025-09-04 13:07 ` Krzysztof Kozlowski
2025-09-04 14:50 ` Konrad Dybcio
2025-09-05 10:13 ` Sarthak Garg
2025-09-03 8:24 ` [PATCH V5 0/4] Add level shifter support for qualcomm SOC's Dragan Simic
2025-09-03 20:42 ` Rob Herring
2025-09-04 5:28 ` Dragan Simic
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=23c29fb7-c0a4-4519-9b8d-e68255b83a10@kernel.org \
--to=krzk@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@oss.qualcomm.com \
--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=linux-mmc@vger.kernel.org \
--cc=quic_bhaskarv@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_pragalla@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=quic_sartgarg@quicinc.com \
--cc=quic_sayalil@quicinc.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@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;
as well as URLs for NNTP newsgroup(s).