Commit d8bcf4db authored by Viresh Kumar's avatar Viresh Kumar Committed by Greg Kroah-Hartman

arch_topology: Get rid of cap_parsing_done

There is no need to check for cap_parsing_done flag anymore as
!raw_capacity flag alone is enough for us. Remove the (now) useless flag
cap_parsing_done.
Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: default avatarJuri Lelli <juri.lelli@arm.com>
Tested-by: default avatarJuri Lelli <juri.lelli@arm.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 62de1161
...@@ -167,7 +167,6 @@ bool __init topology_parse_cpu_capacity(struct device_node *cpu_node, int cpu) ...@@ -167,7 +167,6 @@ bool __init topology_parse_cpu_capacity(struct device_node *cpu_node, int cpu)
#ifdef CONFIG_CPU_FREQ #ifdef CONFIG_CPU_FREQ
static cpumask_var_t cpus_to_visit; static cpumask_var_t cpus_to_visit;
static bool cap_parsing_done;
static void parsing_done_workfn(struct work_struct *work); static void parsing_done_workfn(struct work_struct *work);
static DECLARE_WORK(parsing_done_work, parsing_done_workfn); static DECLARE_WORK(parsing_done_work, parsing_done_workfn);
...@@ -179,7 +178,7 @@ init_cpu_capacity_callback(struct notifier_block *nb, ...@@ -179,7 +178,7 @@ init_cpu_capacity_callback(struct notifier_block *nb,
struct cpufreq_policy *policy = data; struct cpufreq_policy *policy = data;
int cpu; int cpu;
if (!raw_capacity || cap_parsing_done) if (!raw_capacity)
return 0; return 0;
if (val != CPUFREQ_NOTIFY) if (val != CPUFREQ_NOTIFY)
...@@ -201,7 +200,6 @@ init_cpu_capacity_callback(struct notifier_block *nb, ...@@ -201,7 +200,6 @@ init_cpu_capacity_callback(struct notifier_block *nb,
topology_normalize_cpu_scale(); topology_normalize_cpu_scale();
free_raw_capacity(); free_raw_capacity();
pr_debug("cpu_capacity: parsing done\n"); pr_debug("cpu_capacity: parsing done\n");
cap_parsing_done = true;
schedule_work(&parsing_done_work); schedule_work(&parsing_done_work);
} }
......
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