Re: [PATCH v4 3/8] PM / devfreq: Use the available min/max frequency

2017-10-17 Thread Chanwoo Choi
On 2017년 10월 18일 10:31, Chanwoo Choi wrote: > Hi, > > On 2017년 10월 17일 23:43, MyungJoo Ham wrote: >> On Fri, Oct 13, 2017 at 4:48 PM, Chanwoo Choi wrote: >>> The commit a76caf55e5b35 ("thermal: Add devfreq cooling") is able >>> to disable OPP as a cooling device. In result, both update_devfreq()

Re: [PATCH v4 3/8] PM / devfreq: Use the available min/max frequency

2017-10-17 Thread Chanwoo Choi
Hi, On 2017년 10월 17일 23:43, MyungJoo Ham wrote: > On Fri, Oct 13, 2017 at 4:48 PM, Chanwoo Choi wrote: >> The commit a76caf55e5b35 ("thermal: Add devfreq cooling") is able >> to disable OPP as a cooling device. In result, both update_devfreq() >> and {min|max}_freq_show() have to consider the 'op

Re: [PATCH v4 3/8] PM / devfreq: Use the available min/max frequency

2017-10-17 Thread MyungJoo Ham
On Fri, Oct 13, 2017 at 4:48 PM, Chanwoo Choi wrote: > The commit a76caf55e5b35 ("thermal: Add devfreq cooling") is able > to disable OPP as a cooling device. In result, both update_devfreq() > and {min|max}_freq_show() have to consider the 'opp->available' > status of each OPP. > > So, this patch

[PATCH v4 3/8] PM / devfreq: Use the available min/max frequency

2017-10-13 Thread Chanwoo Choi
The commit a76caf55e5b35 ("thermal: Add devfreq cooling") is able to disable OPP as a cooling device. In result, both update_devfreq() and {min|max}_freq_show() have to consider the 'opp->available' status of each OPP. So, this patch adds the 'scaling_{min|max}_freq' to struct devfreq in order to