From: Deepak Sikri <deepak.sikri@st.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Shiraz HASHIM <shiraz.hashim@st.com>, "rjw@sisk.pl" <rjw@sisk.pl>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
spear-devel <spear-devel@list.st.com>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Mike Turquette <mturquette@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] cpufreq: SPEAr: Add CPUFreq driver
Date: Tue, 27 Nov 2012 09:46:43 +0530 [thread overview]
Message-ID: <50B43EAB.80602@st.com> (raw)
In-Reply-To: <CAKohpomSAogQVeBQ8HaWwwoTVCsMha5d_1Wid6N3t5SnVZTc=w@mail.gmail.com>
On 11/27/2012 9:28 AM, Viresh Kumar wrote:
>>> [snip..]
>>> It's a little bit unusual that cpu runs such a freq range
>>> (166 ~ 600 MHz) at a fixed voltage. You really have no way
>>> to scale voltage?
> AFAIK, there is no voltage scaling.
>
> @Shiraz/Deepak: Can you confirm?
We do not have any provision for voltage scaling in SPEAr.
Deepak
WARNING: multiple messages have this Message-ID (diff)
From: deepak.sikri@st.com (Deepak Sikri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: SPEAr: Add CPUFreq driver
Date: Tue, 27 Nov 2012 09:46:43 +0530 [thread overview]
Message-ID: <50B43EAB.80602@st.com> (raw)
In-Reply-To: <CAKohpomSAogQVeBQ8HaWwwoTVCsMha5d_1Wid6N3t5SnVZTc=w@mail.gmail.com>
On 11/27/2012 9:28 AM, Viresh Kumar wrote:
>>> [snip..]
>>> It's a little bit unusual that cpu runs such a freq range
>>> (166 ~ 600 MHz) at a fixed voltage. You really have no way
>>> to scale voltage?
> AFAIK, there is no voltage scaling.
>
> @Shiraz/Deepak: Can you confirm?
We do not have any provision for voltage scaling in SPEAr.
Deepak
next prev parent reply other threads:[~2012-11-27 4:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 19:39 [PATCH] cpufreq: SPEAr: Add CPUFreq driver Viresh Kumar
2012-11-24 19:39 ` Viresh Kumar
2012-11-24 20:45 ` Rafael J. Wysocki
2012-11-24 20:45 ` Rafael J. Wysocki
2012-11-27 4:01 ` Shawn Guo
2012-11-27 4:01 ` Shawn Guo
2012-11-27 4:01 ` Shawn Guo
2012-11-27 3:58 ` Viresh Kumar
2012-11-27 3:58 ` Viresh Kumar
2012-11-27 4:16 ` Deepak Sikri [this message]
2012-11-27 4:16 ` Deepak Sikri
2012-11-27 5:16 ` Shawn Guo
2012-11-27 5:16 ` Shawn Guo
2012-11-27 4:53 ` Viresh Kumar
2012-11-27 4:53 ` Viresh Kumar
2012-11-27 11:38 ` Rafael J. Wysocki
2012-11-27 11:38 ` Rafael J. Wysocki
2012-11-27 11:35 ` Viresh Kumar
2012-11-27 11:35 ` Viresh Kumar
2012-11-27 12:06 ` Rafael J. Wysocki
2012-11-27 12:06 ` Rafael J. Wysocki
2012-11-27 9:24 ` Sudeep K N
2012-11-27 9:24 ` Sudeep K N
2012-11-27 9:33 ` Viresh Kumar
2012-11-27 9:33 ` Viresh Kumar
2012-11-27 11:19 ` Sudeep K N
2012-11-27 11:19 ` Sudeep K N
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=50B43EAB.80602@st.com \
--to=deepak.sikri@st.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mturquette@linaro.org \
--cc=rjw@sisk.pl \
--cc=shawn.guo@linaro.org \
--cc=shiraz.hashim@st.com \
--cc=spear-devel@list.st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.