On 06/17/2013 02:27 PM, Tomi Valkeinen wrote: > On 17/06/13 14:18, Tony Lindgren wrote: > >> You should be able to get the regulator based on the name just fine >> from the drivers even if one driver is using DT and one is not. That is >> as long as the regulator is defined. Then the regulator fwk will track >> the usecount properly. > > Doesn't the regulator need to be "bound" to a device for the driver to > use the proper name for the regulator? I mean, in this case the dvi > driver wants to get a regulator named "vdd_5v" (or something like that, > I'm not sure what's the proper name). The USB host driver uses a name > "vcc", while the real name of the regulator is "hsusbX_vcc".
Right. I think if the regulator is not bound to any device then you can get it just by supply name. http://lxr.free-electrons.com/source/drivers/regulator/core.c#L1175 But the USB PHY driver will always try to get the regulator for it's device that has supply name "vcc". cheers, -roger -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
