linux-kernel - Re: [PATCH V3 1/4] ufs: dt-bindings: Document gear and rate limit properties

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <25844eea-a41c-4a36-b132-8824e629568d@kernel.org>
Date: Thu, 28 Aug 2025 19:40:55 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Bart Van Assche <bvanassche@....org>,
 Ram Kumar Dwivedi <quic_rdwivedi@...cinc.com>, alim.akhtar@...sung.com,
 avri.altman@....com, robh@...nel.org, krzk+dt@...nel.org,
 conor+dt@...nel.org, mani@...nel.org, James.Bottomley@...senPartnership.com,
 martin.petersen@...cle.com
Cc: linux-scsi@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH V3 1/4] ufs: dt-bindings: Document gear and rate limit
 properties

On 26/08/2025 17:35, Bart Van Assche wrote:
> 
>> +  limit-rate:
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    enum: [1, 2]
>> +    default: 2
>> +    description:
>> +      Restricts the UFS controller to Rate A (1) or Rate B (2) for both
>> +      TX and RX directions, often required in automotive environments due
>> +      to hardware limitations.
> 
> As far as I know no numeric values are associated with these rates in
> the UFSHCI 4.1 standard nor in any of the previous versions of this
> standard. Does the .yaml syntax support something like "enum: [A, B]"?

That's what I also requested and answer was "1" and "2" are coming from
the spec. So now I am confused.


Best regards,
Krzysztof