Messages in this thread | | | Date | Tue, 12 Nov 2019 16:30:36 -0800 | From | Bjorn Andersson <> | Subject | Re: [PATCH v4 6/6] cpufreq: qcom-hw: Move driver initialisation earlier |
| |
On Fri 18 Oct 01:52 PDT 2019, Amit Kucheria wrote:
> Allow qcom-hw driver to initialise 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>
Hi Amit,
Booting linux-next on my db845c (and SDM850 laptop) I can see that the device probes in /sys/bus/platform/drivers/qcom-cpufreq-hw, but /sys/devices/system/cpu/cpufreq is empty.
Reverting this change gives me cpufreq back. Can you please have a look at this?
Regards, Bjorn
> --- > drivers/cpufreq/qcom-cpufreq-hw.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c > index a9ae2f84a4efc..fc92a8842e252 100644 > --- a/drivers/cpufreq/qcom-cpufreq-hw.c > +++ b/drivers/cpufreq/qcom-cpufreq-hw.c > @@ -334,7 +334,7 @@ static int __init qcom_cpufreq_hw_init(void) > { > 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) > { > -- > 2.17.1 >
| |