linux-kernel - Re: [PATCH 1/5] regulator: dt-bindings: Unify compatible

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: <ZjtrmqtB0GuLZRt5@finisterre.sirena.org.uk>
Date: Wed, 8 May 2024 21:10:02 +0900
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>
Cc: Neha Malcom Francis <n-francis@...com>, conor+dt@...nel.org,
	krzk+dt@...nel.org, kristo@...nel.org, vigneshr@...com, nm@...com,
	lgirdwood@...il.com, marten.lindahl@...s.com,
	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, u-kumar1@...com
Subject: Re: [PATCH 1/5] regulator: dt-bindings: Unify compatible

On Tue, May 07, 2024 at 04:11:12PM -0500, Rob Herring wrote:
> On Tue, May 07, 2024 at 05:51:54PM +0530, Neha Malcom Francis wrote:
> > TPS62870/1/2/3 devices have different output currents (6A/9A/12A/15A) of
> > the TPS6287x family. The I2C addresses are the same between them. There
> > is no need for different compatibles for each for these devices so drop
> > them and add a unified "ti,tps6287x" compatible.

> And s/w will never need to know what the max output current is?

Yes, this seems destructive of information for no gain - if anything it
makes things harder to use since you can't just use the part number and
instead have to know about the wildcard.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)