linux-kernel - Re: [PATCH 1/6] regulator: mcp16502: Add supplier for regulators

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 for Android: free password hash cracker in your pocket

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

Message-ID: <e0db4f2b-ce4f-4560-b586-1d8dbb75c7ff@sirena.org.uk>
Date: Fri, 2 Aug 2024 18:58:31 +0100
From: Mark Brown <broonie@...nel.org>
To: Andrei.Simion@...rochip.com
Cc: lgirdwood@...il.com, claudiu.beznea@...on.dev,
	Nicolas.Ferre@...rochip.com, krzk+dt@...nel.org,
	conor+dt@...nel.org, robh@...nel.org, alexandre.belloni@...tlin.com,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, Mihai.Sain@...rochip.com
Subject: Re: [PATCH 1/6] regulator: mcp16502: Add supplier for regulators

On Fri, Aug 02, 2024 at 02:25:15PM +0000, Andrei.Simion@...rochip.com wrote:

> In regulator.yaml exists .*-supply [1] which practically allows every
> char sequence before -supply. In the binding microchip,mcp16502.yaml [2]
> each node under the regulators includes all the rules/documentation
> from regulator.yaml , so I supposed that it is unnecessary to add
> in the binding of those new property.

> What is your opinion? Let me know any thoughts.

The specific names for a given device are supposed to be specified,
there's a bunch of existing bindings that appear to do that.

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