From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] cpufreq-dt: support cluster level clock
Date: Tue, 3 Mar 2015 22:03:31 +0800 [thread overview]
Message-ID: <20150303140331.GA11325@leoy-linaro> (raw)
In-Reply-To: <CAKohpoksXwMRWYzSBmbV1nN5_LvUiB1Y2wfgOcCJPx+oipaXZw@mail.gmail.com>
On Tue, Mar 03, 2015 at 06:40:23PM +0530, Viresh Kumar wrote:
> On 3 March 2015 at 18:33, Leo Yan <leo.yan@linaro.org> wrote:
> > In the previous code, cpufreq-dt driver support single clock shared by
> > all CPUs or every CPU has dedicated clock; but it cannot support cluster
> > level clock domain, which is very common implementation for ARM SoCs.
> >
> > So this patch add the support for cluster level clock; which use the
> > platform parameter "clk_domain_boundary" to indicate whether the clock
> > domain is bound to system level, cluster level or CPU level.
> >
> > Signed-off-by: Leo Yan <leo.yan@linaro.org>
>
> No. We aren't going to do it this way. You just test your current SoC where
> all CPUs share clock line. The other SoC that might come later, where
> clocks are per cluster, can be handled later.
>
> So, for now you don't need any changes in the driver I believe.
Correct, current SoC shares one clock line.
I'm just thinking to finish things in one time. From my previous
experience, clocks per cluster are common cases for ARM's
multi-clusters, so i think it's reasonable to add related support.
Regarding of testing this patch, i created two virtual clocks for
every cluster and passed the test. Do u think this is acceptable?
Thanks,
Leo Yan
next prev parent reply other threads:[~2015-03-03 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 13:03 [PATCH 0/2] cpufreq-dt: support for cluster level clock Leo Yan
2015-03-03 13:03 ` [PATCH 1/2] cpufreq-dt: support " Leo Yan
2015-03-03 13:10 ` Viresh Kumar
2015-03-03 14:03 ` Leo Yan [this message]
2015-03-03 15:19 ` Viresh Kumar
2015-03-04 2:35 ` Leo Yan
2015-03-03 13:03 ` [PATCH 2/2] ARM: mvebu: update cpufreq-dt's platform data Leo Yan
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=20150303140331.GA11325@leoy-linaro \
--to=leo.yan@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).