Re: [PATCH 3/6] cpufreq: Remove the has_target() check from notifier handler
From: Rafael J. Wysocki
Date: Wed Jun 19 2019 - 08:31:04 EST
On Wed, Jun 19, 2019 at 1:35 PM Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
>
> cpufreq_notify_transition() is only called for has_target() type driver
> and not for set_policy type, and the check is simply redundant. Remove
> it.
Ah, OK
So this patch removes a check introduced by the previous one. :-)
Please merge them together.
> Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> ---
> drivers/cpufreq/cpufreq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index e59194c2c613..41ac701e324f 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -359,7 +359,7 @@ static void cpufreq_notify_transition(struct cpufreq_policy *policy,
> * which is not equal to what the cpufreq core thinks is
> * "old frequency".
> */
> - if (has_target() && policy->cur && policy->cur != freqs->old) {
> + if (policy->cur && policy->cur != freqs->old) {
> pr_debug("Warning: CPU frequency is %u, cpufreq assumed %u kHz\n",
> freqs->old, policy->cur);
> freqs->old = policy->cur;
> --
> 2.21.0.rc0.269.g1a574e7a288b
>