From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add a generic cpufreq-cpu0 driver
Date: Thu, 19 Jul 2012 23:54:38 +0800 [thread overview]
Message-ID: <1342713281-31114-1-git-send-email-shawn.guo@linaro.org> (raw)
This is a continuous effort of Richard's work [1]. But that generic
cpufreq driver has been rewritten with taking omap-cpufreq.c as the
reference to adopt OPP library.
Same as Richard's patch, the driver has no intention to support the
multi-core systems that frequency and voltage can be scaled
independently on different CPUs. Instead, it aims at uniprocessor (UP)
and those symmetric multiprocessor (SMP) systems which share clock and
voltage across all CPUs.
I have seen patch from Mike changing omap-cpufreq driver to scale
regulator from clk notifier. We can definitely make the same move
for cpufreq-cpu0 later when the patch gets accepted.
Regards,
Shawn
[1] http://thread.gmane.org/gmane.linux.kernel.cpufreq/7688/focus=7688
---
Richard Zhao (1):
ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp
Shawn Guo (2):
PM / OPP: Initialize OPP table from device tree
cpufreq: Add a generic cpufreq-cpu0 driver
.../devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 58 +++++
Documentation/devicetree/bindings/power/opp.txt | 29 +++
arch/arm/kernel/smp.c | 54 +++++
drivers/base/power/opp.c | 66 ++++++
drivers/cpufreq/Kconfig | 11 +
drivers/cpufreq/Makefile | 2 +
drivers/cpufreq/cpufreq-cpu0.c | 235 ++++++++++++++++++++
include/linux/opp.h | 4 +
8 files changed, 459 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt
create mode 100644 Documentation/devicetree/bindings/power/opp.txt
create mode 100644 drivers/cpufreq/cpufreq-cpu0.c
--
1.7.5.4
next reply other threads:[~2012-07-19 15:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 15:54 Shawn Guo [this message]
2012-07-19 15:54 ` [PATCH 1/3] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Shawn Guo
2012-07-20 6:36 ` Shilimkar, Santosh
2012-07-20 7:56 ` Shawn Guo
2012-07-20 8:27 ` Shilimkar, Santosh
2012-07-19 15:54 ` [PATCH 2/3] PM / OPP: Initialize OPP table from device tree Shawn Guo
2012-07-20 6:00 ` Menon, Nishanth
2012-07-20 8:46 ` Shawn Guo
2012-07-20 9:04 ` Menon, Nishanth
2012-07-19 15:54 ` [PATCH 3/3] cpufreq: Add a generic cpufreq-cpu0 driver Shawn Guo
2012-07-20 6:52 ` Shilimkar, Santosh
2012-07-20 12:33 ` Shawn Guo
2012-07-20 15:50 ` Turquette, Mike
2012-07-21 5:04 ` Shilimkar, Santosh
2012-07-21 6:38 ` Shawn Guo
2012-07-27 2:04 ` Richard Zhao
2012-07-30 4:57 ` Shawn Guo
2012-07-20 12:51 ` Richard Zhao
2012-07-20 13:15 ` Shawn Guo
2012-07-26 13:11 ` Mark Brown
2012-07-27 2:13 ` Richard Zhao
2012-07-27 10:08 ` Mark Brown
2012-07-30 6:52 ` Shawn Guo
2012-07-30 8:20 ` Shawn Guo
2012-07-30 18:55 ` Mark Brown
2012-07-30 18:53 ` Mark Brown
2012-07-31 4:20 ` Shawn Guo
2012-07-31 13:40 ` Mark Brown
2012-07-27 6:33 ` Richard Zhao
2012-07-30 8:17 ` Shawn Guo
2012-07-30 8:50 ` Richard Zhao
2012-07-30 9:24 ` Shawn Guo
2012-07-19 18:39 ` [PATCH 0/3] " Rafael J. Wysocki
2012-07-20 0:29 ` Shawn Guo
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=1342713281-31114-1-git-send-email-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).