From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] cpufreq: OMAP: move to drivers/cpufreq and updates for v3.3
Date: Fri, 18 Nov 2011 13:20:23 -0800 [thread overview]
Message-ID: <871ut5w2js.fsf@ti.com> (raw)
Hi Dave,
Here's the updated pull request after a rebase onto v3.2-rc1 and some
fixes to address other changes that went into v3.2.
This is targetted for v3.3, so I'd like to get it into your tree and
into linux-next.
Also, let me know if you want a MAINTAINERS entry for this file, as I'm
happy to maintain it.
Kevin
The following changes since commit 1ea6b8f48918282bdca0b32a34095504ee65bab5:
Linux 3.2-rc1 (2011-11-07 16:16:02 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.3/omap-cpufreq
Colin Cross (1):
cpufreq: OMAP: notify even with bad boot frequency
Kevin Hilman (1):
cpufreq: OMAP: fixup for omap_device changes, include <linux/module.h>
Nishanth Menon (6):
cpufreq: OMAP: move clk name decision to init
cpufreq: OMAP: deny initialization if no mpudev
cpufreq: OMAP: dont support !freq_table
cpufreq: OMAP: only supports OPP library
cpufreq: OMAP: put clk if cpu_init failed
cpufreq: OMAP: fix freq_table leak
Russell King (1):
cpufreq: OMAP: Add SMP support for OMAP4+
Santosh Shilimkar (1):
cpufreq: OMAP: cleanup for multi-SoC support, move into drivers/cpufreq
Todd Poynor (1):
cpufreq: OMAP: Enable all CPUs in shared policy mask
arch/arm/plat-omap/Makefile | 1 -
arch/arm/plat-omap/cpu-omap.c | 171 -------------------------
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/omap-cpufreq.c | 274 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 275 insertions(+), 172 deletions(-)
delete mode 100644 arch/arm/plat-omap/cpu-omap.c
create mode 100644 drivers/cpufreq/omap-cpufreq.c
next reply other threads:[~2011-11-18 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 21:20 Kevin Hilman [this message]
2011-12-02 17:45 ` [GIT PULL] cpufreq: OMAP: move to drivers/cpufreq and updates for v3.3 Kevin Hilman
2011-12-02 17:52 ` Dave Jones
2011-12-02 19:45 ` Dave Jones
2011-12-02 21:19 ` Kevin Hilman
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=871ut5w2js.fsf@ti.com \
--to=khilman@ti.com \
--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).