From: "Cousson, Benoit" <b-cousson-l0cyMroinI0@public.gmane.org>
To: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
Cc: linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
catalin.marinas-5wv7dgnIgG8@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
cpufreq-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org,
Richard Zhao
<richard.zhao-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
eric.miao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH V6 4/7] cpufreq: add clk-reg cpufreq driver
Date: Fri, 13 Jan 2012 18:16:18 +0100 [thread overview]
Message-ID: <4F1066E2.1020804@ti.com> (raw)
In-Reply-To: <874nw0sfdn.fsf-l0cyMroinI0@public.gmane.org>
On 1/12/2012 11:52 PM, Kevin Hilman wrote:
> Richard Zhao<richard.zhao-KZfg59tc24xl57MIdRCFDg@public.gmane.org> writes:
[...]
>> Do you have real case to need different voltage/clk?
>
> Sure, any system with independently scalable CPUs/clusters.
AFAIK, in the ARM SoC world there is a least the MSM8660 that does
support that today.
Regards,
Benoit
next prev parent reply other threads:[~2012-01-13 17:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 2:56 [PATCH V6 0/7] add a generic cpufreq driver Richard Zhao
2011-12-30 2:56 ` [PATCH V6 1/7] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Richard Zhao
2011-12-30 2:56 ` [PATCH V6 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate " Richard Zhao
2012-01-06 0:56 ` Richard Zhao
2012-01-06 13:19 ` Shawn Guo
2011-12-30 2:56 ` [PATCH V6 3/7] cpufreq: OMAP: " Richard Zhao
2012-01-06 1:02 ` Richard Zhao
2011-12-30 2:56 ` [PATCH V6 4/7] cpufreq: add clk-reg cpufreq driver Richard Zhao
2012-01-11 23:22 ` Kevin Hilman
2012-01-12 8:23 ` Richard Zhao
2012-01-12 22:52 ` Kevin Hilman
[not found] ` <874nw0sfdn.fsf-l0cyMroinI0@public.gmane.org>
2012-01-13 17:16 ` Cousson, Benoit [this message]
2011-12-30 2:56 ` [PATCH V6 5/7] dts/imx6q: add cpufreq property Richard Zhao
2011-12-30 2:56 ` [PATCH V6 6/7] arm/imx6q: register arm_clk as cpu to clkdev Richard Zhao
2011-12-30 2:56 ` [PATCH V6 7/7] arm/imx6q: select ARCH_HAS_CPUFREQ Richard Zhao
2012-01-04 22:16 ` [PATCH V6 0/7] add a generic cpufreq driver Richard Zhao
2012-01-06 0:53 ` Richard Zhao
2012-01-09 14:52 ` Richard Zhao
2012-02-03 16:28 ` Russell King - ARM Linux
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=4F1066E2.1020804@ti.com \
--to=b-cousson-l0cymroini0@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=cpufreq-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=eric.miao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=khilman-l0cyMroinI0@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org \
--cc=richard.zhao-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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).