From: richard.zhao@linaro.org (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 0/7] add a generic cpufreq driver
Date: Fri, 30 Dec 2011 10:56:02 +0800 [thread overview]
Message-ID: <1325213769-11752-1-git-send-email-richard.zhao@linaro.org> (raw)
The driver is based on clock and regulator APIs and support single core
and multi core ARM SoCs. For multi core, it assume all cores share the
same clock and voltage.
Thanks Arnd, Mark, Jamie, Shawn, Rob, for your review.
Changes in V6:
- add scaling_available_freqs
Changes in V5:
- add more comments
- rename trans-latency to clk-trans-latency, and it only describe clk
latency. Regulator latency is got from regulator_set_voltage_time.
Changes in v4:
- add depends on HAVE_CLK && OF && REGULATOR
- add set_cpu_freq fail check
- regulator_put wehn module exit
- add pr_fmt and convert all printk to pr_xxx
- use voltage range
- comment and doc fix
- add cpu_volts value pre-check in module init
- add helpfull module parameter max_freq
- remove compatible string check on Arnd's comment.
- remove generic-cpufreq to clk-reg-cpufreq
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 V6 1/7] ARM: add cpufreq transiton notifier to adjust
[PATCH V6 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate
[PATCH V6 3/7] cpufreq: OMAP: remove loops_per_jiffy recalculate for
[PATCH V6 4/7] cpufreq: add clk-reg cpufreq driver
[PATCH V6 5/7] dts/imx6q: add cpufreq property
[PATCH V6 6/7] arm/imx6q: register arm_clk as cpu to clkdev
[PATCH V6 7/7] arm/imx6q: select ARCH_HAS_CPUFREQ
Thanks
Richard
next reply other threads:[~2011-12-30 2:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 2:56 Richard Zhao [this message]
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
2012-01-13 17:16 ` Cousson, Benoit
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=1325213769-11752-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).