Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753532AbaGNGa2 (ORCPT ); Mon, 14 Jul 2014 02:30:28 -0400 Received: from mail-ob0-f181.google.com ([209.85.214.181]:39499 "EHLO mail-ob0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750864AbaGNGaP (ORCPT ); Mon, 14 Jul 2014 02:30:15 -0400 MIME-Version: 1.0 In-Reply-To: <1405319337-11368-1-git-send-email-xerofoify@gmail.com> References: <1405319337-11368-1-git-send-email-xerofoify@gmail.com> Date: Mon, 14 Jul 2014 12:00:14 +0530 Message-ID: Subject: Re: [PATCH] cpufreq: Fix latency for cpufreq_info From: Viresh Kumar To: Nicholas Krause Cc: "Rafael J. Wysocki" , "linux-pm@vger.kernel.org" , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14 July 2014 11:58, Nicholas Krause wrote: > This fixes the latency for the cpufreq policy to 1 million nanoseconds > that calls the function pxa_cpu_init for the member of the structure > called cpuinfo.transition_latency. > > Signed-off-by: Nicholas Krause > --- > drivers/cpufreq/pxa2xx-cpufreq.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/cpufreq/pxa2xx-cpufreq.c b/drivers/cpufreq/pxa2xx-cpufreq.c > index e24269a..e08bb98 100644 > --- a/drivers/cpufreq/pxa2xx-cpufreq.c > +++ b/drivers/cpufreq/pxa2xx-cpufreq.c > @@ -372,7 +372,7 @@ static int pxa_cpufreq_init(struct cpufreq_policy *policy) > init_sdram_rows(); > > /* set default policy and cpuinfo */ > - policy->cpuinfo.transition_latency = 1000; /* FIXME: 1 ms, assumed */ > + policy->cpuinfo.transition_latency = 1000000; > > /* Generate pxa25x the run cpufreq_frequency_table struct */ > for (i = 0; i < NUM_PXA25x_RUN_FREQS; i++) { Acked-by: Viresh Kumar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/