PM / devfreq: passive: Keep cpufreq_policy for possible cpus
authorChanwoo Choi <cw00.choi@samsung.com>
Tue, 26 Apr 2022 18:49:19 +0000 (03:49 +0900)
committerChanwoo Choi <cw00.choi@samsung.com>
Tue, 17 May 2022 09:24:39 +0000 (18:24 +0900)
commit26984d9d581e5049bd75091d2e789b9cc3ea12e0
tree5d74ce9b6da36e719bd3db3b0c0cf11662df0a56
parent05723e71234b60a1a47313ea1a889797ec648f1c
PM / devfreq: passive: Keep cpufreq_policy for possible cpus

The passive governor requires the cpu data to get the next target frequency
of devfreq device if depending on cpu. In order to reduce the unnecessary
memory data, keep cpufreq_policy data for possible cpus instead of NR_CPU.

Tested-by: Chen-Yu Tsai <wenst@chromium.org>
Tested-by: Johnson Wang <johnson.wang@mediatek.com>
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
drivers/devfreq/governor.h
drivers/devfreq/governor_passive.c
include/linux/devfreq.h