From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Manivannan Sadhasivam <mani@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com, bvanassche@acm.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com, agross@kernel.org,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sa8155: Add gear and rate limit properties to UFS
Date: Tue, 5 Aug 2025 15:16:33 +0200 [thread overview]
Message-ID: <11ea828a-6d35-4ac6-a207-0284870c28fc@oss.qualcomm.com> (raw)
In-Reply-To: <2nm7xurqgzrnffustrsmswy2rbug6geadaho42qlb7tr2jirlr@uw5gaery445y>
On 8/1/25 2:19 PM, Manivannan Sadhasivam wrote:
> On Fri, Aug 01, 2025 at 11:12:42AM GMT, Krzysztof Kozlowski wrote:
>> On 01/08/2025 11:10, Ram Kumar Dwivedi wrote:
>>>
>>>
>>> On 01-Aug-25 1:58 PM, Manivannan Sadhasivam wrote:
>>>> On Thu, Jul 24, 2025 at 09:48:53AM GMT, Krzysztof Kozlowski wrote:
>>>>> On 22/07/2025 18:11, Ram Kumar Dwivedi wrote:
>>>>>> Add optional limit-hs-gear and limit-rate properties to the UFS node to
>>>>>> support automotive use cases that require limiting the maximum Tx/Rx HS
>>>>>> gear and rate due to hardware constraints.
>>>>>
>>>>> What hardware constraints? This needs to be clearly documented.
>>>>>
>>>>
>>>> Ram, both Krzysztof and I asked this question, but you never bothered to reply,
>>>> but keep on responding to other comments. This won't help you to get this series
>>>> merged in any form.
>>>>
>>>> Please address *all* review comments before posting next iteration.
>>>
>>> Hi Mani,
>>>
>>> Apologies for the delay in responding.
>>> I had planned to explain the hardware constraints in the next patchset’s commit message, which is why I didn’t reply earlier.
>>>
>>> To clarify: the limitations are due to customer board designs, not our SoC. Some boards can't support higher gear operation, hence the need for optional limit-hs-gear and limit-rate properties.
>>>
>>
>> That's vague and does not justify the property. You need to document
>> instead hardware capabilities or characteristic. Or explain why they
>> cannot. With such form I will object to your next patch.
>>
>
> I had an offline chat with Ram and got clarified on what these properties are.
> The problem here is not with the SoC, but with the board design. On some Qcom
> customer designs, both the UFS controller in the SoC and the UFS device are
> capable of operating at higher gears (say G5). But due to board constraints like
> poor thermal dissipation, routing loss, the board cannot efficiently operate at
> the higher speeds.
>
> So the customers wanted a way to limit the gear speed (say G3) and rate
> (say Mode-A) on the specific board DTS.
I'm not necessarily saying no, but have you explored sysfs for this?
I suppose it may be too late (if the driver would e.g. init the UFS
at max gear/rate at probe time, it could cause havoc as it tries to
load the userland)..
Konrad
next prev parent reply other threads:[~2025-08-05 13:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 16:11 [PATCH V1 0/3] Add DT-based gear and rate limiting support Ram Kumar Dwivedi
2025-07-22 16:11 ` [PATCH 1/3] ufs: ufs-qcom: Add support for DT-based gear and rate limiting Ram Kumar Dwivedi
2025-07-22 18:54 ` Dmitry Baryshkov
2025-07-24 7:35 ` Ram Kumar Dwivedi
2025-07-24 8:41 ` Dmitry Baryshkov
2025-07-31 16:28 ` Ram Kumar Dwivedi
2025-07-31 17:43 ` Dmitry Baryshkov
2025-07-24 7:49 ` Krzysztof Kozlowski
2025-07-22 16:11 ` [PATCH 2/3] arm64: dts: qcom: sa8155: Add gear and rate limit properties to UFS Ram Kumar Dwivedi
2025-07-22 18:55 ` Dmitry Baryshkov
2025-07-24 7:36 ` Ram Kumar Dwivedi
2025-07-24 7:48 ` Krzysztof Kozlowski
2025-08-01 8:28 ` Manivannan Sadhasivam
2025-08-01 9:04 ` Krzysztof Kozlowski
2025-08-01 9:19 ` Ram Kumar Dwivedi
2025-08-01 9:10 ` Ram Kumar Dwivedi
2025-08-01 9:12 ` Krzysztof Kozlowski
2025-08-01 12:19 ` Manivannan Sadhasivam
2025-08-05 13:16 ` Konrad Dybcio [this message]
2025-08-05 16:55 ` Manivannan Sadhasivam
2025-08-05 17:06 ` Konrad Dybcio
2025-08-05 17:19 ` Manivannan Sadhasivam
2025-08-05 17:19 ` Alim Akhtar
2025-08-05 17:22 ` 'Manivannan Sadhasivam'
2025-08-05 17:36 ` Alim Akhtar
2025-08-05 17:40 ` Konrad Dybcio
2025-08-05 17:52 ` Alim Akhtar
2025-08-05 18:26 ` Konrad Dybcio
2025-08-06 4:21 ` Alim Akhtar
2025-08-06 5:05 ` 'Manivannan Sadhasivam'
2025-08-06 5:46 ` Alim Akhtar
2025-08-06 11:25 ` 'Manivannan Sadhasivam'
2025-08-07 16:38 ` Alim Akhtar
2025-08-08 12:43 ` 'Manivannan Sadhasivam'
2025-08-08 15:08 ` Alim Akhtar
2025-08-08 18:06 ` 'Manivannan Sadhasivam'
2025-08-09 1:00 ` Alim Akhtar
2025-08-09 11:13 ` 'Manivannan Sadhasivam'
2025-08-11 21:45 ` Nitin Rawat
2025-09-03 4:06 ` Alim Akhtar
2025-07-22 16:11 ` [PATCH 3/3] dt-bindings: ufs: qcom: Document HS gear and rate limit properties Ram Kumar Dwivedi
2025-07-22 18:31 ` Rob Herring (Arm)
2025-07-22 19:02 ` Dmitry Baryshkov
2025-07-24 7:36 ` Ram Kumar Dwivedi
2025-07-24 7:48 ` Krzysztof Kozlowski
2025-07-23 14:41 ` [PATCH V1 0/3] Add DT-based gear and rate limiting support Manivannan Sadhasivam
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=11ea828a-6d35-4ac6-a207-0284870c28fc@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_rdwivedi@quicinc.com \
--cc=robh@kernel.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