From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Jesper Nilsson <jesper.nilsson@axis.com>,
Eric Miao <eric.y.miao@gmail.com>,
linux-cris-kernel@axis.com,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Miao Steven <realmz6@gmail.com>,
linux-sh@vger.kernel.org, Sekhar Nori <nsekhar@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Mikael Starvik <starvik@axis.com>,
Paul Mundt <lethal@linux-sh.org>,
sparclinux@vger.kernel.org, Dave Jones <davej@redhat.com>,
David Miller <davem@davemloft.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
John Crispin <blogic@openwrt.org>
Subject: Re: [Query] CPUFreq: Does these machines have separate clock domains for CPUs?
Date: Fri, 30 Aug 2013 18:49:24 +1000 [thread overview]
Message-ID: <1377852564.3978.0.camel@pasglop> (raw)
In-Reply-To: <CAKohponWn-RN7-6sdhghd6RGCOd357G+TKLsxHfqnSCuMD7xxw@mail.gmail.com>
On Thu, 2013-08-29 at 15:45 +0530, Viresh Kumar wrote:
> drivers/cpufreq/pmac32-cpufreq.c
This is always UP.
Cheers,
Ben.
prev parent reply other threads:[~2013-08-30 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 10:15 [Query] CPUFreq: Does these machines have separate clock domains for CPUs? Viresh Kumar
2013-08-29 10:23 ` Sekhar Nori
2013-08-29 10:30 ` Viresh Kumar
2013-08-29 10:27 ` Sekhar Nori
2013-08-29 10:33 ` Viresh Kumar
2013-08-29 22:41 ` Aaro Koskinen
2013-08-30 4:21 ` Mikael Starvik
2013-08-30 6:48 ` Magnus Damm
2013-08-30 7:33 ` Viresh Kumar
2013-09-04 7:27 ` Magnus Damm
2013-08-30 8:49 ` Benjamin Herrenschmidt [this message]
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=1377852564.3978.0.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=blogic@openwrt.org \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.y.miao@gmail.com \
--cc=jesper.nilsson@axis.com \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=realmz6@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=starvik@axis.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;
as well as URLs for NNTP newsgroup(s).