From: santosh.shilimkar@ti•com (Santosh Shilimkar)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC] cpufreq: Add bindings for CPU clock sharing topology
Date: Mon, 21 Jul 2014 09:40:32 -0400 [thread overview]
Message-ID: <53CD1850.8000904@ti.com> (raw)
In-Reply-To: <CAKohpok-C+JCebjJkZExx6EjBctoyJF7fV71Vjj7bi1TAdXrFQ@mail.gmail.com>
On Sunday 20 July 2014 08:07 AM, Viresh Kumar wrote:
> On 19 July 2014 20:54, Santosh Shilimkar <santosh.shilimkar@ti•com> wrote:
>> Sorry for jumping late
>
> No, you aren't late. Its just 2 days old thread :)
>
>> but one of the point I was raising as part of your
>> other series was to extend the CPU topology bindings to cover the voltage
>> domain information which is probably what is really needed to let the
>> CPUfreq extract the information. Not sure if it was already discussed.
>
> Not it wasn't.
>
>> After all the CPU clocks, cluster, clock-gating, power domains are pretty much
>> related. So instead of having new binding for CPUFreq, I was wondering whether
>> we can extend the CPU topology binding information to include missing information.
>> Scheduler work anyway needs that information.
>>
>> Ref: Documentation/devicetree/bindings/arm/topology.txt
>>
>> Does that make sense ?
>
> Yeah it does, but I am not sure what exactly the bindings should look then.
> So, the most basic step could be moving the new bindings to topology.txt
> and name clock-master to dvfs-master.
>
> What else?
>
> If its going to be much controversial then we *can* go for just dvfs bindings
> for now and then update them later.
>
Would be good to get others opinion. As you said if it is controversial then
it will stall the development.
Regards,
Santosh
next prev parent reply other threads:[~2014-07-21 13:40 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 [this message]
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
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=53CD1850.8000904@ti.com \
--to=santosh.shilimkar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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