[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171122110830.GA4084@vireshk-i7>
Date: Wed, 22 Nov 2017 16:38:30 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Javi Merino <javi.merino@...nel.org>
Cc: Eduardo Valentin <edubezval@...il.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Lukasz Luba <llu.ker.dev@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Ionela Voinescu <ionela.voinescu@....com>,
Punit Agrawal <punit.agrawal@....com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Amit Daniel Kachhap <amit.kachhap@...il.com>,
Zhang Rui <rui.zhang@...el.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Linux PM <linux-pm@...r.kernel.org>,
Lukasz Luba <lukasz.luba@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] cpu_cooling: Drop static-power related stuff
On 22-11-17, 06:55, Viresh Kumar wrote:
> On 21-11-17, 18:00, Javi Merino wrote:
> > As Ionela pointed out earlier in the thread, the cpufreq driver for Juno
> > was not acceptable for mainline because it used platform specific code.
>
> Can we get a link to that thread? I don't remember what I have commented earlier
> but the above doesn't seem to be entirely true.
>
> The basic idea is to use as much common stuff as possible and so to use
> cpufreq-dt.c if possible. Its not that we are against platform specific bits,
> they are fine if they are really required.
Just to correct everyone here, Juno doesn't use the cpufreq-dt driver but
scpi-cpufreq.c :)
--
viresh
Powered by blists - more mailing lists