From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 5/6] clk: pxa: transfer CPU clock setting from pxa2xx-cpufreq
Date: Wed, 19 Oct 2016 22:15:43 +0200 [thread overview]
Message-ID: <877f943xjk.fsf@belgarion.home> (raw)
In-Reply-To: <20161018234855.GO8871@codeaurora.org> (Stephen Boyd's message of "Tue, 18 Oct 2016 16:48:55 -0700")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 10/18, Robert Jarzmik wrote:
>> Robert Jarzmik <robert.jarzmik@free.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
next prev parent reply other threads:[~2016-10-19 20:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 20:09 [PATCH 0/6] Make pxa core clocks settable Robert Jarzmik
2016-10-10 20:09 ` [PATCH 1/6] clk: pxa: remove unused variables Robert Jarzmik
2016-10-10 20:09 ` [PATCH 2/6] clk: pxa: core pll is not affected by t bit Robert Jarzmik
2016-10-10 20:09 ` [PATCH 3/6] clk: pxa: b bit of clkcfg means fast bus Robert Jarzmik
2016-10-10 20:09 ` [PATCH 4/6] clk: pxa: export core clocks Robert Jarzmik
2016-10-10 20:09 ` [PATCH 5/6] clk: pxa: transfer CPU clock setting from pxa2xx-cpufreq Robert Jarzmik
2016-10-18 7:00 ` Robert Jarzmik
2016-10-18 23:48 ` Stephen Boyd
2016-10-19 20:15 ` Robert Jarzmik [this message]
2016-10-19 20:51 ` Stephen Boyd
2016-10-20 3:44 ` Viresh Kumar
2016-10-10 20:09 ` [PATCH 6/6] cpufreq: pxa: convert to clock API Robert Jarzmik
2016-10-12 2:36 ` Viresh Kumar
2016-10-12 6:22 ` Robert Jarzmik
2016-10-12 6:32 ` Viresh Kumar
2016-10-12 8:29 ` Robert Jarzmik
2016-10-12 8:40 ` Viresh Kumar
2016-10-12 19:12 ` Robert Jarzmik
2016-10-15 19:42 ` Robert Jarzmik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877f943xjk.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®