On Mon, May 09, 2022 at 06:38:05PM +0200, Andrew Lunn wrote: > So we have a collection of regulators, varying in numbers between > different PHYs, with different vendor names and purposes. In general, > they all should be turned on. Yet we want them named so it is clear > what is going on. > Is there a generic solution here so that the phylib core can somehow > enumerate them and turn them on, without actually knowing what they > are called because they have vendor specific names in order to be > clear what they are? > There must be a solution to this, phylib cannot be the first subsystem > to have this requirement, so if you could point to an example, that > would be great. No, it's not really come up much before - generally things with regulator control that have generic drivers tend not to be sophisticated enough to have more than one supply, or to be on an enumerable bus where the power is part of the bus specification so have the power specified as part of the bus. You'd need to extend the regulator bindings to support parallel array of phandles and array of names properties like clocks have as an option like you were asking for, which would doubtless be fun for validation but is probably the thing here.
Attachment:
signature.asc
Description: PGP signature
