[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <df2aa27f-0130-4b03-8a9b-e21067ea4f92@quicinc.com>
Date: Tue, 26 Aug 2025 20:23:45 +0530
From: Ram Kumar Dwivedi <quic_rdwivedi@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: <mani@...nel.org>, <alim.akhtar@...sung.com>, <avri.altman@....com>,
<bvanassche@....org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>, <andersson@...nel.org>,
<konradybcio@...nel.org>, <agross@...nel.org>,
<James.Bottomley@...senpartnership.com>, <martin.petersen@...cle.com>,
<linux-arm-msm@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2 1/4] ufs: dt-bindings: Document gear and rate limit
properties
On 24-Aug-25 2:59 PM, Krzysztof Kozlowski wrote:
> On Thu, Aug 21, 2025 at 03:46:06PM +0530, Ram Kumar Dwivedi wrote:
>> + limit-hs-gear:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + minimum: 1
>> + maximum: 5
>
> default:
Hi Krzysztof,
I will add it in next patchset
Thanks,
Ram.
>
>> + description:
>> + Restricts the maximum HS gear used in both TX and RX directions,
>> + typically for hardware or power constraints in automotive use cases.
>> +
>> + limit-rate:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + enum: [1, 2]
>
> default:
I will add it in next patchset
Thanks,
Ram.>
>> + description:
>> + Restricts the UFS controller to Rate A (1) or Rate B (2) for both
>
> Is 1 and 2 known in UFS spec? Feels like you wanted here string for 'a'
> and 'b'.
Yes, 1 and 2 is mentioned in MIPI Unipro(UFS Interconnect layer) spec.
Thanks,
Ram.
>
> Best regards,
> Krzysztof
>
Powered by blists - more mailing lists