On Tue, Nov 15, 2022 at 07:36:01AM +, 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.
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
On Tue, Nov 15, 2022 at 11:16:53AM +, Mark Brown wrote:
> On Tue, Nov 15, 2022 at 10:42:50AM +, Russell King (Oracle) wrote:
> > On Tue, Nov 15, 2022 at 10:34:41AM +, Mark Brown wrote:
>
> > > Well, it's not making this maintainer happy :/ If we know what
> > > PHY is there why not
On Tue, Nov 15, 2022 at 10:42:50AM +, Russell King (Oracle) wrote:
> On Tue, Nov 15, 2022 at 10:34:41AM +, Mark Brown wrote:
> > Well, it's not making this maintainer happy :/ If we know what
> > PHY is there why not just look up the set of supplies based on
> > the compatible of the
On Tue, Nov 15, 2022 at 11:18:50AM +0100, Corentin LABBE wrote:
> Le Tue, Nov 15, 2022 at 10:03:14AM +, Mark Brown a écrit :
> > 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.
> The
On Tue, Nov 15, 2022 at 07:36:01AM +, 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?
