[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877f943xjk.fsf@belgarion.home>
Date: Wed, 19 Oct 2016 22:15:43 +0200
From: Robert Jarzmik <robert.jarzmik@...e.fr>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Michael Turquette <mturquette@...libre.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH 5/6] clk: pxa: transfer CPU clock setting from pxa2xx-cpufreq
Stephen Boyd <sboyd@...eaurora.org> writes:
> On 10/18, Robert Jarzmik wrote:
>> Robert Jarzmik <robert.jarzmik@...e.fr> writes:
>> Hi Michael and Stephen,
>>
>> I'm planing on sending a v2 next week with minor corrections, mostly in the data
>> tables (pxa25x_freqs and pxa27x_freqs), as testing prooved some values were wrong.
>>
>> If you want me modify this serie, will you have time to review for next week or
>> should I delay the v2 posting ?
>>
>
> No need to delay. clk patches look fine with a quick glance. It
> would be really neat if we could make cpufreq-dt work without DT.
> What's blocking that? OPP tables?
Heu I'm not the author of cpufreq-dt, so I'm not the best to answer.
To answer the question "without DT", it depends if you mean "with ACPI" or "with
platform_data" or something else.
>From what I've seen so far, the missing/blocking points are :
- the OPP points definition as you said
- probably same thing for the input power supply / regulator
- the cooling parts probably
- and more generaly all the cpufreq-dt is built around device-tree
- last point, the name from KConfig, "Generic DT based cpufreq driver"
=> that strongly suggest it's device-tree only
I'm deeply convinced that Viresh being one of the authors will shed more light
on this.
Cheers.
--
Robert
Powered by blists - more mailing lists