From: Leo Yan <leo.yan@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] cpufreq-dt: support cluster level clock
Date: Wed, 4 Mar 2015 10:35:47 +0800 [thread overview]
Message-ID: <20150304023547.GB21106@leoy-linaro> (raw)
In-Reply-To: <CAKohponQ1keZ3x9mK=9qchfwPF=cYKAA9aYgmu52X5NDGJLECg@mail.gmail.com>
On Tue, Mar 03, 2015 at 08:49:25PM +0530, Viresh Kumar wrote:
> On 3 March 2015 at 19:33, Leo Yan <leo.yan@linaro.org> wrote:
> > 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.
>
> Yes they are common, but that will be fixed with new OPP bindings
> I am working on [1].
Good to know this and looking forward the patches...
> > Regarding of testing this patch, i created two virtual clocks for
> > every cluster and passed the test. Do u think this is acceptable?
>
> Just to confirm again, we aren't going to accept or apply these
> patches. It will work without any changes for you, for now.
OK, i will go back to just support for the case of one clock source.
> --
> viresh
>
> [1] https://www.marc.info/?l=linaro-kernel&m=142364262800650&w=3
next prev parent reply other threads:[~2015-03-04 2:35 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
2015-03-03 15:19 ` Viresh Kumar
2015-03-04 2:35 ` Leo Yan [this message]
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=20150304023547.GB21106@leoy-linaro \
--to=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=thomas.petazzoni@free-electrons.com \
--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