Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933784Ab3HHCmu (ORCPT ); Wed, 7 Aug 2013 22:42:50 -0400 Received: from mail-qc0-f172.google.com ([209.85.216.172]:63953 "EHLO mail-qc0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933682Ab3HHCmt (ORCPT ); Wed, 7 Aug 2013 22:42:49 -0400 MIME-Version: 1.0 In-Reply-To: <52029713.5070808@wwwdotorg.org> References: <8d192a13cb7e088943da40689d62bc6353bd8604.1375886595.git.viresh.kumar@linaro.org> <52028620.6000608@wwwdotorg.org> <52028859.20008@wwwdotorg.org> <52029713.5070808@wwwdotorg.org> Date: Thu, 8 Aug 2013 08:12:48 +0530 Message-ID: Subject: Re: [PATCH 1/6] clk: Tegra: Add CPU0 clock driver From: Viresh Kumar To: Stephen Warren Cc: rjw@sisk.pl, swarren@nvidia.com, linaro-kernel@lists.linaro.org, patches@linaro.org, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, mturquette@linaro.org, linux-arm-kernel@lists.infradead.org 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: 1036 Lines: 24 On 8 August 2013 00:20, Stephen Warren wrote: > Right, and that's *exactly* what having a cpufreq driver is for; to > implement the details of CPU clock management. cpufreq drivers used to keep such information since a long time, probably because there wasn't another place to keep them and provide generic API's (like generic clock framework).. And so this replication started to get in place which we are trying to get rid of now. All cpufreq drivers share a lot of common code which can go away and so cpufreq-cpu0 was introduced.. With this patchset this replication goes away for tegra atleast at the cost of a platform specific clk-cpu driver.. I think that's a good deal, isn't it? And that's the only way you can use these generic drivers that we have... -- 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/