[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mvia6q8p.fsf@belgarion.home>
Date: Wed, 12 Oct 2016 08:22:30 +0200
From: Robert Jarzmik <robert.jarzmik@...e.fr>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH 6/6] cpufreq: pxa: convert to clock API
Viresh Kumar <viresh.kumar@...aro.org> writes:
> On 10-10-16, 22:09, Robert Jarzmik wrote:
>> As the clock settings have been introduced into the clock pxa drivers,
>> which are now available to change the CPU clock by themselves, remove
>> the clock handling from this driver, and rely on pxa clock drivers.
>>
>> Signed-off-by: Robert Jarzmik <robert.jarzmik@...e.fr>
>> ---
>> drivers/cpufreq/pxa2xx-cpufreq.c | 191 ++++++++-------------------------------
>> 1 file changed, 39 insertions(+), 152 deletions(-)
>
> As you mentioned in the previous patch, why can't you use cpufreq-dt
> driver now and delete this one ?
PXA architecture have both legacy platform_data based configurations and new
devicetree based ones.
I don't think cpufreq-dt can handle the legacy platform_data ones, can it ?
Cheers.
--
Robert
Powered by blists - more mailing lists