From: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] cpufreq: arm-big-little: use clk_get instead of clk_get_sys
Date: Thu, 03 Oct 2013 10:23:08 +0100 [thread overview]
Message-ID: <524D377C.90200@arm.com> (raw)
In-Reply-To: <CAKohpo=90LQawdZGmm2-CU3U-kHL6uUkmFKGRGZFCwY5YckLEg@mail.gmail.com>
On 03/10/13 10:00, Viresh Kumar wrote:
> On 3 October 2013 14:27, Sudeep KarkadaNagesha
> <Sudeep.KarkadaNagesha@arm.com> wrote:
>> Agreed, but there's no cluster node in DT. So platforms using DT would have
>> these clocks in cpu@n node as it's used for CPU frequency scaling. One example I
>> can see is highbank(it uses cpufreq-cpu0 meaning its single cluster clock). So
>> AFAICT if any big-little systems wants to pass cluster clocks through DT, it has
>> to be cpu@n nodes. Let me know if you have any alternate thoughts ?
>
> I understand your point, but shouldn't we name it then: cpu clock?
> Probably cluster clock was wrong from the beginning.. As there is no cluster clock,
> or there is ? :)
>
Ok I would phrase it as, it's a clock shared by all the cpus in the cluster.
So like any other shared clocks in the system, each device sharing it would have
it as input clock but it would be single clock output from the clock/power
controller. Does it make any sense ?
Regards,
Sudeep
next prev parent reply other threads:[~2013-10-03 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 9:30 [PATCH] cpufreq: arm-big-little: use clk_get instead of clk_get_sys Sudeep KarkadaNagesha
2013-10-03 4:52 ` Viresh Kumar
2013-10-03 8:57 ` Sudeep KarkadaNagesha
2013-10-03 9:00 ` Viresh Kumar
2013-10-03 9:23 ` Sudeep KarkadaNagesha [this message]
2013-10-03 9:38 ` Viresh Kumar
2013-10-03 9:50 ` Sudeep KarkadaNagesha
2013-10-03 9:58 ` 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=524D377C.90200@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--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