>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/ >max_freq. > >Needless to say that this change is a NOP, intended to improve >readability. > >Signed-off-by: Matthias Kaehlcke <m...@chromium.org> >Reviewed-by: Chanwoo Choi <cw00.c...@samsung.com> >Reviewed-by: Brian Norris <briannor...@chromium.org> >--- >Changes in v5: >- none > >Changes in v4: >- added 'Reviewed-by: Brian Norris <briannor...@chromium.org>' tag > >Changes in v3: >- none > >Changes in v2: >- added 'Reviewed-by: Chanwoo Choi <cw00.c...@samsung.com>' tag >--- > drivers/devfreq/devfreq.c | 12 ++++++------ > 1 file changed, 6 insertions(+), 6 deletions(-)
Acked-by: MyungJoo Ham <myungjoo....@samsung.com> This can be applied independently from other commits in this series.