Re: [PATCH v5 3/5] thermal: devfreq_cooling: Use PM QoS to set frequency limits

2020-04-06 Thread Daniel Lezcano
On 03/04/2020 19:18, Matthias Kaehlcke wrote: > Hi Daniel, > > On Fri, Apr 03, 2020 at 06:43:20PM +0200, Daniel Lezcano wrote: >> On 18/03/2020 12:45, Lukasz Luba wrote: >>> From: Matthias Kaehlcke >>> >>> Now that devfreq supports limiting the frequency range of a device >>> through PM QoS make

Re: [PATCH v5 3/5] thermal: devfreq_cooling: Use PM QoS to set frequency limits

2020-04-06 Thread Daniel Lezcano
On 18/03/2020 12:45, Lukasz Luba wrote: > From: Matthias Kaehlcke > > Now that devfreq supports limiting the frequency range of a device > through PM QoS make use of it instead of disabling OPPs that should > not be used. > > The switch from disabling OPPs to PM QoS introduces a subtle behaviora

Re: [PATCH v5 3/5] thermal: devfreq_cooling: Use PM QoS to set frequency limits

2020-04-03 Thread Matthias Kaehlcke
Hi Daniel, On Fri, Apr 03, 2020 at 06:43:20PM +0200, Daniel Lezcano wrote: > On 18/03/2020 12:45, Lukasz Luba wrote: > > From: Matthias Kaehlcke > > > > Now that devfreq supports limiting the frequency range of a device > > through PM QoS make use of it instead of disabling OPPs that should > >

[PATCH v5 3/5] thermal: devfreq_cooling: Use PM QoS to set frequency limits

2020-03-19 Thread Lukasz Luba
From: Matthias Kaehlcke Now that devfreq supports limiting the frequency range of a device through PM QoS make use of it instead of disabling OPPs that should not be used. The switch from disabling OPPs to PM QoS introduces a subtle behavioral change in case of conflicting requests (min > max):