Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S968390Ab3HJHp5 (ORCPT ); Sat, 10 Aug 2013 03:45:57 -0400 Received: from mail-oa0-f50.google.com ([209.85.219.50]:53711 "EHLO mail-oa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S968352Ab3HJHpz (ORCPT ); Sat, 10 Aug 2013 03:45:55 -0400 MIME-Version: 1.0 In-Reply-To: <149222df041360bac7bb58a9f9baa5f5b8277445.1376116345.git.viresh.kumar@linaro.org> References: <149222df041360bac7bb58a9f9baa5f5b8277445.1376116345.git.viresh.kumar@linaro.org> Date: Sat, 10 Aug 2013 13:15:54 +0530 Message-ID: Subject: Re: [PATCH 44/44] cpufreq: pass suitable index instead of freq to cpufreq_driver->target() From: Viresh Kumar To: rjw@sisk.pl Cc: linaro-kernel@lists.linaro.org, patches@linaro.org, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Viresh Kumar Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 870 Lines: 17 On 10 August 2013 12:14, Viresh Kumar wrote: > This tries to remove code redundancy from cpufreq driver by moving some common > part of them to the core. Each driver calls cpufreq_frequency_table_target() to > get a suitable index for a target frequency and then works on it. Its better to > do this at core level before calling cpufreq driver and hence passing "index" > instead of "target_freq and relation" to cpufreq_driver->target() routine. > > Signed-off-by: Viresh Kumar > --- This one is sent by mistake.. It isn't ready yet and will be sent separately later. :( -- 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/