> No, that's not a thing - the supplies are individual, named properties > and even if there were a list we'd still want them to be named so it's > clear what's going on. 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. Thanks Andrew
