From: richard.zhao@linaro.org (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/7] add a generic cpufreq driver
Date: Mon, 19 Dec 2011 11:21:36 +0800 [thread overview]
Message-ID: <1324264903-15395-1-git-send-email-richard.zhao@linaro.org> (raw)
The driver support single core and multi core ARM SoCs. For multi core,
it assume all cores share the same clock and voltage.
TODO:
- Add each core seperate freq/volt support (MSM).
Changes in v3:
- move adjusting smp loops_per_jiffy to arm common code,
and also adjust global loops_per_jiffy.
- remove adjusting loops_per_jiffy in imx and omap cpufreq drivers.
- check compatible "generic-cpufreq" when module_init
- change printk to pr_xxx
- add generic-cpufreq DT binding doc
Changes in v2:
- add volatage change support
- change '_' in property name to '-'
- use initial value to calculate loops_per_jiffy
- fix reading cpu_volts property bug
- let cpufreq_frequency_table_cpuinfo routines handle cpu_freq_khz_max/min
- don't change freq in arm_cpufreq_exit, because every core share the same freq.
- use unsigned long describe frequency as much as possible. Because clk use
unsigned long, but cpufreq use unsigned int.
[PATCH V3 1/7] ARM: add cpufreq transiton notifier to adjust
[PATCH V3 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate
[PATCH V3 3/7] cpufreq: OMAP: remove loops_per_jiffy recalculate for
[PATCH V3 4/7] cpufreq: add generic cpufreq driver
[PATCH V3 5/7] dts/imx6q: add cpufreq property
[PATCH V3 6/7] arm/imx6q: register arm_clk as cpu to clkdev
[PATCH V3 7/7] arm/imx6q: select ARCH_HAS_CPUFREQ
next reply other threads:[~2011-12-19 3:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 3:21 Richard Zhao [this message]
2011-12-19 3:21 ` [PATCH V3 1/7] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Richard Zhao
2011-12-21 14:21 ` Richard Zhao
2011-12-19 3:21 ` [PATCH V3 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate " Richard Zhao
2011-12-19 3:21 ` [PATCH V3 3/7] cpufreq: OMAP: " Richard Zhao
2011-12-19 3:21 ` [PATCH V3 4/7] cpufreq: add generic cpufreq driver Richard Zhao
2011-12-19 10:05 ` Jamie Iles
2011-12-19 14:19 ` Richard Zhao
2011-12-19 14:39 ` Jamie Iles
2011-12-19 15:00 ` Rob Herring
2011-12-20 1:59 ` Richard Zhao
2011-12-20 15:13 ` Rob Herring
2011-12-20 15:21 ` Arnd Bergmann
2011-12-20 14:59 ` Mark Brown
2011-12-20 23:27 ` Richard Zhao
2011-12-20 23:48 ` Mark Brown
2011-12-21 1:20 ` Richard Zhao
2011-12-21 1:32 ` Mark Brown
2011-12-21 2:24 ` Richard Zhao
2011-12-21 2:33 ` Mark Brown
2011-12-21 2:51 ` Richard Zhao
2011-12-21 9:27 ` Richard Zhao
2011-12-21 9:43 ` Arnd Bergmann
2011-12-21 11:44 ` Kay Sievers
2011-12-21 12:12 ` Mark Brown
2011-12-21 12:49 ` Kay Sievers
2011-12-21 14:19 ` Richard Zhao
2011-12-22 0:50 ` Mark Brown
2011-12-21 12:11 ` Mark Brown
2011-12-19 3:21 ` [PATCH V3 5/7] dts/imx6q: add cpufreq property Richard Zhao
2011-12-19 3:21 ` [PATCH V3 6/7] arm/imx6q: register arm_clk as cpu to clkdev Richard Zhao
2011-12-19 3:21 ` [PATCH V3 7/7] arm/imx6q: select ARCH_HAS_CPUFREQ Richard Zhao
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=1324264903-15395-1-git-send-email-richard.zhao@linaro.org \
--to=richard.zhao@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).