cpufreq: qcom-hw: Remove un-necessary cpumask_empty() check

CPUFreq core will always set the "policy->cpus" bitmask with the bitfield
of the CPU that goes first per domain/policy. So there is no way the
"policy->cpus" bitmask will be empty during qcom_cpufreq_hw_cpu_init().

Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c
index 833589b..61850d7 100644 (file)
--- a/drivers/cpufreq/qcom-cpufreq-hw.c
+++ b/drivers/cpufreq/qcom-cpufreq-hw.c
@@ -566,11 +566,6 @@ static int qcom_cpufreq_hw_cpu_init(struct cpufreq_policy *policy)
                data->per_core_dcvs = true;
 
        qcom_get_related_cpus(index, policy->cpus);
-       if (cpumask_empty(policy->cpus)) {
-               dev_err(dev, "Domain-%d failed to get related CPUs\n", index);
-               ret = -ENOENT;
-               goto error;
-       }
 
        policy->driver_data = data;
        policy->dvfs_possible_from_any_cpu = true;