From: Viresh Kumar <viresh.kumar@linaro.org>
To: Pi-Cheng Chen <pi-cheng.chen@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Mike Turquette <mturquette@linaro.org>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Eddie Huang <eddie.huang@mediatek.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>
Subject: Re: [PATCH 1/2] cpufreq-dt: check CPU clock/power domain during initializing
Date: Tue, 20 Jan 2015 13:09:35 +0530 [thread overview]
Message-ID: <CAKohponUfB-RJTwPDMPCGogng8nzc=kwTF56GjGfDSD7MLQuAg@mail.gmail.com> (raw)
In-Reply-To: <CALx668V5TKkx-qGnMjFAspTQ5pu3XsM1012wXsBHvR3CNsuCew@mail.gmail.com>
On 20 January 2015 at 13:03, Pi-Cheng Chen <pi-cheng.chen@linaro.org> wrote:
> I will also try to add intermediate frequency support in next version.
Sure
> BTW, do you think it's a good idea to add a new device tree binding like
> intermediate_clock = <&clksys MAINPLL>
> and so that cpufreq-dt could get the intermediate clock?
Yeah, we need that. I am trying to implement new opp bindings and will
take care of that. Until that time, use platform data to do that.
--
viresh
next prev parent reply other threads:[~2015-01-20 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 9:54 [PATCH 0/2] cpufreq: add cpufreq driver for Mediatek MT8173 SoC pi-cheng.chen
2015-01-09 9:54 ` [PATCH 1/2] cpufreq-dt: check CPU clock/power domain during initializing pi-cheng.chen
2015-01-19 8:00 ` Viresh Kumar
2015-01-20 7:33 ` Pi-Cheng Chen
2015-01-20 7:39 ` Viresh Kumar [this message]
2015-01-20 8:47 ` Pi-Cheng Chen
2015-01-09 9:54 ` [PATCH 2/2] cpufreq: add cpufreq driver for Mediatek MT8173 SoC pi-cheng.chen
[not found] ` <1421221419.31355.123.camel@mtksdaap41>
2015-01-15 2:02 ` Pi-Cheng Chen
2015-01-19 10:42 ` Viresh Kumar
2015-01-20 7:06 ` Pi-Cheng Chen
2015-01-19 16:00 ` Mike Turquette
2015-01-20 7:18 ` Pi-Cheng Chen
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='CAKohponUfB-RJTwPDMPCGogng8nzc=kwTF56GjGfDSD7MLQuAg@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=eddie.huang@mediatek.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@linaro.org \
--cc=pi-cheng.chen@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=thomas.petazzoni@free-electrons.com \
--cc=yingjoe.chen@mediatek.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
all inboxes | Powered by JetHome®