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: <9944c595-da68-43c0-8364-6a8665a0fc3f@acm.org>
Date: Tue, 26 Aug 2025 08:35:15 -0700
From: Bart Van Assche <bvanassche@....org>
To: 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 8/26/25 8:08 AM, Ram Kumar Dwivedi wrote:
> +  limit-hs-gear:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    minimum: 1
> +    maximum: 5
> +    default: 5
> +    description:
> +      Restricts the maximum HS gear used in both TX and RX directions,
> +      typically for hardware or power constraints in automotive use cases.

The UFSHCI 5.0 spec will add gear 6 soon. So why to restrict the maximum
gear to 5?

> +  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]"?

Thanks,

Bart.