Am Montag, den 26.05.2014, 20:52 +0530 schrieb Viresh Kumar: > On 26 May 2014 19:28, Lucas Stach <l.stach@xxxxxxxxxxxxxx> wrote: > > Right, the OPP in my example define the minimum required voltage for > > each frequency. This is in accordance to the OPP binding. But for this > > chip the datasheet explicitly says that it is ok to power the cpu rail > > with up to 1.4V, regardless of the current operating frequency. So this > > 1.4V is really the upper bound I would like to pass to the regulator > > framework. This ensures that the driver still works properly even if the > > external regulator can't scale down to the minimum (or in other words > > optimal) voltage. > > One more query. You have mentioned earlier and I just wanted to confirm > this. In your platform/board regulator only supports one voltage, i.e. 1.4 uV, > and it we can't get lower values out of regulator ? > > If that's the case, why are you looking to use regulator at all? The platform I'm working on supports cpu rail voltage regulation just fine. I just want to make sure that the driver works properly on platforms where this isn't the case. As the datasheet explicitly allows this case I want to make sure to not introduce a software only restriction, where there isn't any in hardware. Regards, Lucas -- Pengutronix e.K. | Lucas Stach | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
