Re: [PATCH] PM / devfreq: Init user limits from OPP limits, not viceversa

2018-05-17 Thread Chanwoo Choi
Hi, On 2018년 05월 18일 01:35, Matthias Kaehlcke wrote: > On Thu, May 17, 2018 at 10:07:56AM +0900, Chanwoo Choi wrote: >> Hi, >> >> On 2018년 05월 17일 07:57, Matthias Kaehlcke wrote: >>> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding >>> the devfreq device") introduced the initializa

Re: [PATCH] PM / devfreq: Init user limits from OPP limits, not viceversa

2018-05-17 Thread Matthias Kaehlcke
On Thu, May 17, 2018 at 10:07:56AM +0900, Chanwoo Choi wrote: > Hi, > > On 2018년 05월 17일 07:57, Matthias Kaehlcke wrote: > > Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding > > the devfreq device") introduced the initialization of the user > > limits min/max_freq from the lowest/h

Re: [PATCH] PM / devfreq: Init user limits from OPP limits, not viceversa

2018-05-16 Thread Chanwoo Choi
Hi, On 2018년 05월 17일 07:57, Matthias Kaehlcke wrote: > Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding > the devfreq device") introduced the initialization of the user > limits min/max_freq from the lowest/highest available OPPs. Later > commit f1d981eaecf8 ("PM / devfreq: Use the

[PATCH] PM / devfreq: Init user limits from OPP limits, not viceversa

2018-05-16 Thread Matthias Kaehlcke
Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the devfreq device") introduced the initialization of the user limits min/max_freq from the lowest/highest available OPPs. Later commit f1d981eaecf8 ("PM / devfreq: Use the available min/max frequency") added scaling_min/max_freq, whi