From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] cpufreq: Add bindings for CPU clock sharing topology
Date: Mon, 25 Aug 2014 12:35:44 +0530 [thread overview]
Message-ID: <CAKohpo=s9A_EtJ2d2E9sjVkR8xs-bgRisnk=jZUeyWEf3uP5gg@mail.gmail.com> (raw)
In-Reply-To: <20140725200214.22930.56323@quantum>
On 26 July 2014 01:32, Mike Turquette <mike.turquette@linaro.org> wrote:
> So my opinion is to figure out how to specify the shared-clock versus
> independent-clock parameter it DT. I think the big issue here is the
> topology semantics around the cpus node, and I'll stay out of that
> stuff. But let's please not introduce a random API for a single merge
> window and let's also not over-consolidate machine driver code just for
> the sake of having fewer C files.
Returning almost after a month to this :(
- I agree that consolidation to cpufreq-cpu0 driver is good but adding a
backend clk driver for that is bad. I would look around supporting callbacks
to cpufreq-cpu0 driver. So that ->target()/->target_index() can be specified
by platform drivers and rest of the code can be used. But that's the next
problem to solve.
- Back to the first issue. How do we sharing information from DT ?
As I read them (and I may be wrong in understanding that), there were
conflicting ideas from many..
Can we please decide how we want to see these bindings? So, that I can
implement them quickly and close this thread...
Its just hanging in the middle as there wasn't a single clean solution yet.
--
viresh
next prev parent reply other threads:[~2014-08-25 7:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 5:35 [RFC] cpufreq: Add bindings for CPU clock sharing topology Viresh Kumar
2014-07-18 6:17 ` Olof Johansson
2014-07-18 6:40 ` Viresh Kumar
2014-07-18 21:52 ` Olof Johansson
2014-07-19 14:46 ` Viresh Kumar
2014-07-19 15:24 ` Santosh Shilimkar
2014-07-20 12:07 ` Viresh Kumar
2014-07-21 13:40 ` Santosh Shilimkar
2014-07-24 0:33 ` Mike Turquette
2014-07-24 2:24 ` Rob Herring
2014-07-24 10:39 ` Viresh Kumar
2014-07-25 20:02 ` Mike Turquette
2014-08-25 7:05 ` Viresh Kumar [this message]
2014-07-21 17:00 ` Rob Herring
2014-07-23 4:55 ` Viresh Kumar
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='CAKohpo=s9A_EtJ2d2E9sjVkR8xs-bgRisnk=jZUeyWEf3uP5gg@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).