Re: [PATCH V3 07/16] PM / OPP: Add support to parse "operating-points-v2" bindings

2015-07-31 Thread Stephen Boyd
On 07/31, Viresh Kumar wrote: > On 30-07-15, 22:51, Stephen Boyd wrote: > > > + opp->u_volt = microvolt[0]; > > > + opp->u_volt_min = microvolt[1]; > > > + opp->u_volt_max = microvolt[2]; > > > > Should the default be 0 and ULONG_MAX for volt_min/volt_max when > > there's on element? > > I am

Re: [PATCH V3 07/16] PM / OPP: Add support to parse operating-points-v2 bindings

2015-07-31 Thread Stephen Boyd
On 07/31, Viresh Kumar wrote: On 30-07-15, 22:51, Stephen Boyd wrote: + opp-u_volt = microvolt[0]; + opp-u_volt_min = microvolt[1]; + opp-u_volt_max = microvolt[2]; Should the default be 0 and ULONG_MAX for volt_min/volt_max when there's on element? I am not still sure how the

Re: [PATCH V3 07/16] PM / OPP: Add support to parse "operating-points-v2" bindings

2015-07-30 Thread Viresh Kumar
On 30-07-15, 22:51, Stephen Boyd wrote: > > + opp->u_volt = microvolt[0]; > > + opp->u_volt_min = microvolt[1]; > > + opp->u_volt_max = microvolt[2]; > > Should the default be 0 and ULONG_MAX for volt_min/volt_max when > there's on element? I am not still sure how the regulator API is

Re: [PATCH V3 07/16] PM / OPP: Add support to parse "operating-points-v2" bindings

2015-07-30 Thread Stephen Boyd
On 07/29, Viresh Kumar wrote: > This adds support in OPP library to parse and create list of OPPs from > operating-points-v2 bindings. It takes care of most of the properties of > new bindings (except shared-opp, which will be handled separately). > > For backward compatibility, we keep

Re: [PATCH V3 07/16] PM / OPP: Add support to parse operating-points-v2 bindings

2015-07-30 Thread Stephen Boyd
On 07/29, Viresh Kumar wrote: This adds support in OPP library to parse and create list of OPPs from operating-points-v2 bindings. It takes care of most of the properties of new bindings (except shared-opp, which will be handled separately). For backward compatibility, we keep supporting

Re: [PATCH V3 07/16] PM / OPP: Add support to parse operating-points-v2 bindings

2015-07-30 Thread Viresh Kumar
On 30-07-15, 22:51, Stephen Boyd wrote: + opp-u_volt = microvolt[0]; + opp-u_volt_min = microvolt[1]; + opp-u_volt_max = microvolt[2]; Should the default be 0 and ULONG_MAX for volt_min/volt_max when there's on element? I am not still sure how the regulator API is going to look

[PATCH V3 07/16] PM / OPP: Add support to parse "operating-points-v2" bindings

2015-07-29 Thread Viresh Kumar
This adds support in OPP library to parse and create list of OPPs from operating-points-v2 bindings. It takes care of most of the properties of new bindings (except shared-opp, which will be handled separately). For backward compatibility, we keep supporting earlier bindings. We try to search for

[PATCH V3 07/16] PM / OPP: Add support to parse operating-points-v2 bindings

2015-07-29 Thread Viresh Kumar
This adds support in OPP library to parse and create list of OPPs from operating-points-v2 bindings. It takes care of most of the properties of new bindings (except shared-opp, which will be handled separately). For backward compatibility, we keep supporting earlier bindings. We try to search for