[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y3NnirK0bN71IgCo@Red>
Date: Tue, 15 Nov 2022 11:18:50 +0100
From: Corentin LABBE <clabbe@...libre.com>
To: Mark Brown <broonie@...nel.org>
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
Le Tue, Nov 15, 2022 at 10:03:14AM +0000, Mark Brown a écrit :
> 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.
Hello
The device know which supply it have, but I found only this way to made all maintainers happy.
See https://lore.kernel.org/netdev/0518eef1-75a6-fbfe-96d8-bb1fc4e5178a@linaro.org/t/#m7a2e012f4c7c7058478811929774ab2af9bfcbf6
Regards
Powered by blists - more mailing lists