Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751751AbaGKEf7 (ORCPT ); Fri, 11 Jul 2014 00:35:59 -0400 Received: from mail-oa0-f44.google.com ([209.85.219.44]:62613 "EHLO mail-oa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750866AbaGKEf4 (ORCPT ); Fri, 11 Jul 2014 00:35:56 -0400 MIME-Version: 1.0 In-Reply-To: <1405028569-14253-13-git-send-email-ttynkkynen@nvidia.com> References: <1405028569-14253-1-git-send-email-ttynkkynen@nvidia.com> <1405028569-14253-13-git-send-email-ttynkkynen@nvidia.com> Date: Fri, 11 Jul 2014 10:05:56 +0530 Message-ID: Subject: Re: [PATCH 12/13] cpufreq: Add cpufreq driver for Tegra124 From: Viresh Kumar To: Tuomas Tynkkynen Cc: "linux-tegra@vger.kernel.org" , Linux Kernel Mailing List , "linux-arm-kernel@lists.infradead.org" , "linux-pm@vger.kernel.org" , Stephen Warren , Thierry Reding , Peter De Schrijver , Prashant Gaikwad , Mike Turquette , "Rafael J. Wysocki" , "devicetree@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tuomas, On 11 July 2014 03:12, Tuomas Tynkkynen wrote: > Add a new cpufreq driver for Tegra124. Instead of using the PLLX as > the CPU clocksource, switch immediately to the DFLL. It allows the use > of higher clock rates, and will automatically scale the CPU voltage as > well. We also rely on the DFLL driver to determine the CPU clock > frequencies that the chip supports, so that we can directly build a > cpufreq table with the OPP library helper dev_pm_opp_init_cpufreq_table. > > This driver is a completely independent of the old cpufreq driver > (tegra-cpufreq), which is only used on Tegra20. > > Signed-off-by: Tuomas Tynkkynen Please reuse cpufreq-cpu0 instead of adding a new driver. Similar is being adopted by all platforms now: krait, mvebu, etc.. -- 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/