Re: [PATCH 1/4] PM / OPP: Reorganize _generic_set_opp_regulator()

2017-05-22 Thread Stephen Boyd
On 05/17, Viresh Kumar wrote: > The code was overly complicated here because of the limitations that we > had with RCUs (Couldn't use opp-table and OPPs outside RCU protected > section and can't call sleep-able routines from within that). But that > is long gone now. > > Reorganize

Re: [PATCH 1/4] PM / OPP: Reorganize _generic_set_opp_regulator()

2017-05-22 Thread Stephen Boyd
On 05/17, Viresh Kumar wrote: > The code was overly complicated here because of the limitations that we > had with RCUs (Couldn't use opp-table and OPPs outside RCU protected > section and can't call sleep-able routines from within that). But that > is long gone now. > > Reorganize

[PATCH 1/4] PM / OPP: Reorganize _generic_set_opp_regulator()

2017-05-16 Thread Viresh Kumar
The code was overly complicated here because of the limitations that we had with RCUs (Couldn't use opp-table and OPPs outside RCU protected section and can't call sleep-able routines from within that). But that is long gone now. Reorganize _generic_set_opp_regulator() in order to avoid using

[PATCH 1/4] PM / OPP: Reorganize _generic_set_opp_regulator()

2017-05-16 Thread Viresh Kumar
The code was overly complicated here because of the limitations that we had with RCUs (Couldn't use opp-table and OPPs outside RCU protected section and can't call sleep-able routines from within that). But that is long gone now. Reorganize _generic_set_opp_regulator() in order to avoid using