cpufreq: qcom-hw: Move driver initialization earlier
Allow qcom-hw driver to initialize right after the cpufreq and thermal subsystems are initialised in core_initcall so we get earlier access to thermal mitigation. Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org> Acked-by: Taniya Das <tdas@codeaurora.org> Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org> Link: https://lore.kernel.org/r/eacce8d08388b0bdfc908d2701fe7c2b78d90441.1571656015.git.amit.kucheria@linaro.org
This commit is contained in:
parent
b418bab452
commit
11ff4bdd1a
@ -334,7 +334,7 @@ static int __init qcom_cpufreq_hw_init(void)
|
|||||||
{
|
{
|
||||||
return platform_driver_register(&qcom_cpufreq_hw_driver);
|
return platform_driver_register(&qcom_cpufreq_hw_driver);
|
||||||
}
|
}
|
||||||
device_initcall(qcom_cpufreq_hw_init);
|
postcore_initcall(qcom_cpufreq_hw_init);
|
||||||
|
|
||||||
static void __exit qcom_cpufreq_hw_exit(void)
|
static void __exit qcom_cpufreq_hw_exit(void)
|
||||||
{
|
{
|
||||||
|
Loading…
Reference in New Issue
Block a user