From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Add imx6q-cpufreq driver support
Date: Thu, 10 Jan 2013 16:34:21 +0800 [thread overview]
Message-ID: <1357806863-6899-1-git-send-email-shawn.guo@linaro.org> (raw)
Changes since v1:
- Drop patch "PM / OPP: Export more symbols for module usage", as
there is already one "[PATCH 5/6 v9] power: export opp cpufreq
functions" from Mark Langsdorf.
- Instead of having cpu_dev be the struct device retrieved from
get_cpu_device(), have it be &pdev->dev, so that we can use managed
functions to simplified the cleanup path.
- Use dev_* rather than pr_* for message output
- Fix Typos and others commented by Viresh and Sascha.
Once the first patch gets accepted, I will apply the second one for
going through arm-soc tree.
Shawn Guo (2):
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 | 65 +++++++++
drivers/cpufreq/Kconfig.arm | 9 ++
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/imx6q-cpufreq.c | 296 +++++++++++++++++++++++++++++++++++++++
5 files changed, 384 insertions(+), 6 deletions(-)
create mode 100644 drivers/cpufreq/imx6q-cpufreq.c
--
1.7.9.5
next reply other threads:[~2013-01-10 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 8:34 Shawn Guo [this message]
2013-01-10 8:34 ` [PATCH v2 1/2] cpufreq: add imx6q-cpufreq driver Shawn Guo
2013-01-10 8:45 ` Viresh Kumar
2013-01-10 11:55 ` Shawn Guo
2013-01-10 8:34 ` [PATCH v2 2/2] ARM: imx: enable imx6q-cpufreq support Shawn Guo
2013-01-10 10:50 ` Bedia, Vaibhav
2013-01-10 11:07 ` Shawn Guo
2013-01-10 13:02 ` Bedia, Vaibhav
2013-01-10 13:20 ` Shawn Guo
2013-01-10 14:02 ` Bedia, Vaibhav
2013-01-10 14:41 ` Shawn Guo
2013-01-11 4:43 ` Bedia, Vaibhav
2013-01-12 13:34 ` [PATCH v2 0/2] Add imx6q-cpufreq driver support Rafael J. Wysocki
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=1357806863-6899-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).