On 12-01-16, 16:43, Stephen Boyd wrote:
It's far easier to implement, but not far better. In most designs the pin is not called <device_name>-supply, but something more mundane like vdd-supply, vddio-supply, vcc-supply, etc. In the case of CPUs, there's probably nothing in the datasheets, so cpu vs cpu0 is not too important to distinguish here. But for things like a GPU, DSP, video encoder, etc. I doubt it's going to be called <device_name>-supply, so making that the norm is misguided.
I completely agree with that, but here is the usecase: - A OPP-user driver doesn't need to call any special OPP API and OPP layer can allocate the regulator for it using <device>-name. This will make all drivers (that follow this nomenclature in DT) very simple and straight-forward. - But then there are drivers, which need special supply-name. They can always call opp-set-regulator API to mention that, no one is stopping them from that.
And so I still believe, OPP layer has only this option to do it generically.
Comments ?