Commit 8f5783ad authored by Stephen Boyd's avatar Stephen Boyd Committed by Viresh Kumar

cpufreq: qcom-hw: Use optional irq API

Use platform_get_irq_optional() to avoid a noisy error message when the
irq isn't specified. The irq is definitely optional given that we only
care about errors that are -EPROBE_DEFER here.

Cc: Thara Gopinath <thara.gopinath@linaro.org>
Signed-off-by: default avatarStephen Boyd <swboyd@chromium.org>
Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
parent 3ed6dfbd
...@@ -374,9 +374,11 @@ static int qcom_cpufreq_hw_lmh_init(struct cpufreq_policy *policy, int index) ...@@ -374,9 +374,11 @@ static int qcom_cpufreq_hw_lmh_init(struct cpufreq_policy *policy, int index)
* Look for LMh interrupt. If no interrupt line is specified / * Look for LMh interrupt. If no interrupt line is specified /
* if there is an error, allow cpufreq to be enabled as usual. * if there is an error, allow cpufreq to be enabled as usual.
*/ */
data->throttle_irq = platform_get_irq(pdev, index); data->throttle_irq = platform_get_irq_optional(pdev, index);
if (data->throttle_irq <= 0) if (data->throttle_irq == -ENXIO)
return data->throttle_irq == -EPROBE_DEFER ? -EPROBE_DEFER : 0; return 0;
if (data->throttle_irq < 0)
return data->throttle_irq;
data->cancel_throttle = false; data->cancel_throttle = false;
data->policy = policy; data->policy = policy;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment