[lkml]   [2018]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: [PATCH v5 01/12] PM / devfreq: Init user limits from OPP limits, not viceversa
>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, which actually represent
>the frequencies of the lowest/highest available OPP. scaling_min/
>max_freq are initialized with the values from min/max_freq, which
>is totally correct in the context, but a bit awkward to read.
>Swap the initialization and assign scaling_min/max_freq with the
>OPP freqs and then the user limts min/max_freq with scaling_min/
>Needless to say that this change is a NOP, intended to improve
>Signed-off-by: Matthias Kaehlcke <>
>Reviewed-by: Chanwoo Choi <>
>Reviewed-by: Brian Norris <>
>Changes in v5:
>- none
>Changes in v4:
>- added 'Reviewed-by: Brian Norris <>' tag
>Changes in v3:
>- none
>Changes in v2:
>- added 'Reviewed-by: Chanwoo Choi <>' tag
> drivers/devfreq/devfreq.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)

Acked-by: MyungJoo Ham <>

This can be applied independently from other commits in this series.

 \ /
  Last update: 2018-07-04 04:25    [W:0.313 / U:2.436 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site