diff options
| author |  Bjorn Andersson <bjorn.andersson@linaro.org>
| 2022-01-27 19:25:54 -0800 |
|---|---|---|
| committer |  Viresh Kumar <viresh.kumar@linaro.org>
| 2022-02-09 13:18:49 +0530 |
| commit | ef8ee1cb8fc8976a68f5e89cd5f7b6f7de80c66f (patch) | |
| tree | 005a02244cc4753b973132bf86610628fd200d33 /drivers/cpufreq/scmi-cpufreq.c | |
| parent | cpufreq: Reintroduce ready() callback (diff) | |
| download | linux-ef8ee1cb8fc8976a68f5e89cd5f7b6f7de80c66f.tar.gz linux-ef8ee1cb8fc8976a68f5e89cd5f7b6f7de80c66f.tar.bz2 linux-ef8ee1cb8fc8976a68f5e89cd5f7b6f7de80c66f.zip | |
cpufreq: qcom-hw: Delay enabling throttle_irq
In the event that the SoC is under thermal pressure while booting it's
possible for the dcvs notification to happen inbetween the cpufreq
framework calling init and it actually updating the policy's
related_cpus cpumask.
Prior to the introduction of the thermal pressure update helper an empty
cpumask would simply result in the thermal pressure of no cpus being
updated, but the new code will attempt to dereference an invalid per_cpu
variable.
Avoid this problem by using the newly reintroduced "ready" callback, to
postpone enabling the IRQ until the related_cpus cpumask is filled in.
Fixes: 0258cb19c77d ("cpufreq: qcom-cpufreq-hw: Use new thermal pressure update function")
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'drivers/cpufreq/scmi-cpufreq.c')
0 files changed, 0 insertions, 0 deletions