[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpon_YKkRP+iYnUaE14fKmcSx_SfWVHPiA48BGiPTCPHTKA@mail.gmail.com>
Date: Fri, 11 Jul 2014 20:07:42 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Tuomas Tynkkynen <ttynkkynen@...dia.com>
Cc: "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Stephen Warren <swarren@...dotorg.org>,
Thierry Reding <thierry.reding@...il.com>,
Peter De Schrijver <pdeschrijver@...dia.com>,
Prashant Gaikwad <pgaikwad@...dia.com>,
Mike Turquette <mturquette@...aro.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 12/13] cpufreq: Add cpufreq driver for Tegra124
On 11 July 2014 19:44, Tuomas Tynkkynen <ttynkkynen@...dia.com> wrote:
> Sure, I can do the CPU clock parent change first and then instantiate the
> cpufreq-cpu0 driver, like highbank-cpufreq. That'll depend on the patch
> 'cpufreq: cpu0: OPPs can be populated at runtime' from your 'Extend support
> beyond CPU0' series though, any idea when that patch will land in?
So, after your mail I had a chat with Rafael. As this patch happens to be a
fix, we will try to take it into 3.16 only (I am going to send few patches out
of that series separately in few mins). Otherwise 3.17 is where most of it
should go.
Thanks for your agreement to make our life easier :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists