Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750935AbaACFrE (ORCPT ); Fri, 3 Jan 2014 00:47:04 -0500 Received: from mail-oa0-f50.google.com ([209.85.219.50]:62383 "EHLO mail-oa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750769AbaACFrC (ORCPT ); Fri, 3 Jan 2014 00:47:02 -0500 MIME-Version: 1.0 In-Reply-To: <52C548B6.60902@nvidia.com> References: <1387451926-21373-1-git-send-email-bilhuang@nvidia.com> <52B41B18.30302@nvidia.com> <52B41F1B.3030005@nvidia.com> <52B4707F.4040303@wwwdotorg.org> <52C548B6.60902@nvidia.com> Date: Fri, 3 Jan 2014 11:17:00 +0530 Message-ID: Subject: Re: [PATCH v5 1/1] cpufreq: tegra: Re-model Tegra20 cpufreq driver From: Viresh Kumar To: bilhuang , Rob Herring , Grant Likely Cc: Stephen Warren , "Rafael J. Wysocki" , Thierry Reding , Linux Kernel Mailing List , "cpufreq@vger.kernel.org" , "linux-pm@vger.kernel.org" , "linux-tegra@vger.kernel.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: 849 Lines: 21 On 2 January 2014 16:38, bilhuang wrote: > Actually, I don't have plan or resource on doing this, would it be better > that you help to do that instead? Thanks. Point taken. I am there to help if required. So, initially you can just make Tegra work according to the new file we were talking about. I will fix others later. >> I am not sure about the location of such file. Should this be placed in DT >> code somewhere or kept in cpufreq? Rob/Grant ?? >> > Do we have consensus on where to create such file? Not yet, probably people were on leaves. @Grant/Rob: Any inputs here? -- 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/