From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add imx6q-cpufreq driver support
Date: Tue, 8 Jan 2013 14:54:00 +0800 [thread overview]
Message-ID: <1357628043-19256-1-git-send-email-shawn.guo@linaro.org> (raw)
The generic cpufreq-cpu0 driver works well for imx6q before. But it
does not work for 1 GHz and 1.2 GHz operating points the series adds
here. We ended up with having to add an imx6q specific cpufreq driver
to handle those special frequency and voltage scaling requirements for
the new operating points.
I expect patches #1 and #2 go via cpufreq tree and the #3 through
arm-soc tree.
Shawn Guo (3):
PM / OPP: Export more symbols for module usage
cpufreq: add imx6q-cpufreq driver
ARM: imx: enable imx6q-cpufreq support
arch/arm/boot/dts/imx6q.dtsi | 19 ++-
arch/arm/mach-imx/mach-imx6q.c | 64 ++++++++
drivers/base/power/opp.c | 2 +
drivers/cpufreq/Kconfig.arm | 9 ++
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/imx6q-cpufreq.c | 325 +++++++++++++++++++++++++++++++++++++++
6 files changed, 414 insertions(+), 6 deletions(-)
create mode 100644 drivers/cpufreq/imx6q-cpufreq.c
--
1.7.9.5
next reply other threads:[~2013-01-08 6:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 6:54 Shawn Guo [this message]
2013-01-08 6:54 ` [PATCH 1/3] PM / OPP: Export more symbols for module usage Shawn Guo
2013-01-08 14:47 ` Nishanth Menon
2013-01-08 15:06 ` Shawn Guo
2013-01-08 6:54 ` [PATCH 2/3] cpufreq: add imx6q-cpufreq driver Shawn Guo
2013-01-08 8:57 ` Sascha Hauer
2013-01-08 11:28 ` Shawn Guo
2013-01-08 13:10 ` Shawn Guo
2013-01-08 9:16 ` Viresh Kumar
2013-01-08 14:35 ` Shawn Guo
2013-01-08 14:41 ` Viresh Kumar
2013-01-08 15:04 ` Shawn Guo
2013-01-08 15:19 ` Viresh Kumar
2013-01-09 11:25 ` Viresh Kumar
2013-01-08 6:54 ` [PATCH 3/3] ARM: imx: enable imx6q-cpufreq support 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=1357628043-19256-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).