Hi Rafael/Eduardo,
Currently there is no callback for cpufreq drivers which is called once the policy is ready to be used. There are some requirements where such a callback is required.
One of them is registering a cooling device with the help of of_cpufreq_cooling_register(). This routine tries to get 'struct cpufreq_policy' for CPUs which isn't yet initialed at the time ->init() is called and so we face issues while registering the cooling device.
Because we can't register cooling device from ->init(), we need a callback that is called after the policy is ready to be used and hence ->ready() callback.
The first patch fixes few formatting issues, so that the third patch doesn't throw any checkpatch warnings. Second one fixes a potential bug in cpufreq-dt driver. Third one introduces ->ready() callback which will be used in the fourth patch.
V1->V2: - s/usable/ready - dropped last three patches that broke thermal somehow.
Viresh Kumar (4): cpufreq: Fix formatting issues in 'struct cpufreq_driver' cpufreq-dt: pass 'policy->related_cpus' to of_cpufreq_cooling_register() cpufreq: Introduce ->ready() callback for cpufreq drivers cpufreq-dt: register cooling device from ->ready() callback
drivers/cpufreq/cpufreq-dt.c | 51 +++++++++++++++++++++++++---------------- drivers/cpufreq/cpufreq.c | 5 ++++ include/linux/cpufreq.h | 54 ++++++++++++++++++++++++-------------------- 3 files changed, 66 insertions(+), 44 deletions(-)