[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y3Nj4pA2+WRFvSNd@sirena.org.uk>
Date: Tue, 15 Nov 2022 10:03:14 +0000
From: Mark Brown <broonie@...nel.org>
To: Corentin Labbe <clabbe@...libre.com>
Cc: andrew@...n.ch, calvin.johnson@....nxp.com, davem@...emloft.net,
edumazet@...gle.com, hkallweit1@...il.com,
jernej.skrabec@...il.com, krzysztof.kozlowski+dt@...aro.org,
kuba@...nel.org, lgirdwood@...il.com, linux@...linux.org.uk,
pabeni@...hat.com, robh+dt@...nel.org, samuel@...lland.org,
wens@...e.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-sunxi@...ts.linux.dev, netdev@...r.kernel.org,
linux-sunxi@...glegroups.com
Subject: Re: [PATCH v4 1/3] regulator: Add of_regulator_bulk_get_all
On Tue, Nov 15, 2022 at 07:36:01AM +0000, Corentin Labbe wrote:
> It work exactly like regulator_bulk_get() but instead of working on a
> provided list of names, it seek all consumers properties matching
> xxx-supply.
What's the use case - why would a device not know which supplies
it requires? This just looks like an invitation to badly written
consumers TBH.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists