[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOh2x=mjWxSM+WzReHgbnjHmft7yiP6OOf5p-kwpqh2Ykp_O0A@mail.gmail.com>
Date: Thu, 7 Feb 2013 16:03:16 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: dirk.brandewie@...il.com
Cc: linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org
Subject: Re: [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() with drivers
that implement cpufreq_driver.target()
On Wed, Feb 6, 2013 at 10:32 PM, <dirk.brandewie@...il.com> wrote:
> From: Dirk Brandewie <dirk.brandewie@...il.com>
>
> Scaling drivers that implement cpufreq_driver.setpolicy() have
> internal governors that do not signal changes via
> cpufreq_notify_transition() so the frequncy in the policy will almost
> certainly be different than the current frequncy. Only call
> cpufreq_out_of_sync() when the underlying driver implements
> cpufreq_driver.target()
>
> Signed-off-by: Dirk Brandewie <dirk.j.brandewie@...el.com>
> ---
> drivers/cpufreq/cpufreq.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index bb45f93..0ba0344 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -1798,7 +1798,7 @@ int cpufreq_update_policy(unsigned int cpu)
> pr_debug("Driver did not initialize current freq");
> data->cur = policy.cur;
> } else {
> - if (data->cur != policy.cur)
> + if (data->cur != policy.cur && driver->target)
> cpufreq_out_of_sync(cpu, data->cur,
> policy.cur);
Looks much better now :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists