linux-kernel - Re: [PATCH v3] arm64: dts: rockchip: add PCIe3 support on rk3588-jaguar

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] [day] [month] [year] [list]

Message-ID: <148523703cd2dc2e03c102894ebb9870@manjaro.org>
Date: Wed, 24 Apr 2024 18:55:20 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: Quentin Schulz <quentin.schulz@...obroma-systems.com>
Cc: Jonas Karlman <jonas@...boo.se>, Heiko Stuebner <heiko@...ech.de>, Heiko
 Stuebner <heiko.stuebner@...rry.de>, linux-arm-kernel@...ts.infradead.org,
 linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] arm64: dts: rockchip: add PCIe3 support on
 rk3588-jaguar

Hello Quentin,

On 2024-04-23 11:10, Quentin Schulz wrote:
> Wondering if we couldn't have some kind of constant to make it more
> readable in DTSes? E.g.
> 
> #define 1K	1000
> #define 1Ki	1024
> #define 1M	1000000
> #define 1Mi	1048576
> 
> And in the DT we could simply have <(100 * 1M)> wherever appropriate?

Hmm...  Perhaps "<(100M)>" would be even better?  It would require
more thorough changes, though.