From: Leo Yan <leo.yan@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
"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>,
Dan Zhao <dan.zhao@hisilicon.com>,
zhenwei.wang@hisilicon.com, mohaoju@hisilicon.com
Subject: Re: [PATCH 1/2] cpufreq: hisilicon: add acpu driver
Date: Mon, 2 Mar 2015 19:14:07 +0800 [thread overview]
Message-ID: <20150302111406.GA18498@leoy-linaro> (raw)
In-Reply-To: <CAKohpok62tCenCwSRxACeWZGwotsm5sm4nTX74Bq6sAXJfZX0g@mail.gmail.com>
On Mon, Mar 02, 2015 at 04:34:34PM +0530, Viresh Kumar wrote:
> On 2 March 2015 at 16:20, Leo Yan <leo.yan@linaro.org> wrote:
> > i'm glad to use more general method, let me give more input so that we
> > can see if can figure out a better way. ;)
>
> And I am glad to hear that :)
>
> > 1. From hardware design, during the initialization phase, it will
> > bind every opps with its corresponding voltage, and pass these related
> > info to power controller. So later, in kernel the cpufreq driver don't
> > need manually change the voltage, it will only change the cpu clock
> > frequency and power controller will automatically handle voltage
> > related operations. This is similar with TC's SPC implementation.
> >
> > So looks likely the cpufreq-dt driver's voltage related ops are
> > redundant for this case.
>
> Its okay, they wouldn't harm. You don't have to specify any regulator
> in CPUs DT node and the code will not try any fancy stuff :)
If so, it's make sense to directly use cpufreq-dt driver; i will try
it firstly. Appreciate for suggestion :)
Thanks,
Leo Yan
next prev parent reply other threads:[~2015-03-02 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 13:21 [PATCH 0/2] cpufreq: hisilicon acpu support Leo Yan
2015-02-26 13:21 ` [PATCH 1/2] cpufreq: hisilicon: add acpu driver Leo Yan
2015-03-02 6:14 ` Viresh Kumar
2015-03-02 10:50 ` Leo Yan
2015-03-02 11:04 ` Viresh Kumar
2015-03-02 11:14 ` Leo Yan [this message]
2015-02-26 13:21 ` [PATCH 2/2] dt-bindings: cpufreq: document for hisilicon " Leo Yan
2015-03-02 6:16 ` 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=20150302111406.GA18498@leoy-linaro \
--to=leo.yan@linaro.org \
--cc=dan.zhao@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mohaoju@hisilicon.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=zhenwei.wang@hisilicon.com \
/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).