From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/4] OMAP2xxx clock/CPUFreq: fix compilation errors; clean up
Date: Mon, 04 Jan 2010 19:42:04 -0700 [thread overview]
Message-ID: <20100105024113.16275.96273.stgit@localhost.localdomain> (raw)
Hello,
This series fixes several compilation errors for OMAP2xxx chips when
CONFIG_CPU_FREQ is set. These were reported and partially fixed
by Felipe Balbi <felipe.balbi@nokia.com>.
Considerable work is still needed to fully support dynamic frequency
changes on OMAP2xxx-series chips. Readers interested in such a
project are encouraged to review the Maemo Diablo RX-34 and RX-44
kernel source at:
http://repository.maemo.org/pool/diablo/free/k/kernel-source-diablo/
Boot-tested on N800 with n8x0_defconfig with CONFIG_CPU_FREQ; compile-tested
for 2430SDP.
- Paul
---
Felipe Balbi (1):
OMAP2: clock: clk2xxx.c doesn't compile if CPUFREQ is enabled
Paul Walmsley (3):
OMAP2xxx OPP: clean up comments in OPP data
OMAP2 clock: dynamically allocate CPUFreq frequency table
OMAP clock/CPUFreq: avoid leaking the CPUFreq frequency table
arch/arm/mach-omap2/clock2xxx.c | 60 ++++++++++++++++++++++++++-----
arch/arm/mach-omap2/opp2420_data.c | 38 ++++++++++----------
arch/arm/mach-omap2/opp2430_data.c | 30 ++++++++--------
arch/arm/plat-omap/clock.c | 10 +++++
arch/arm/plat-omap/cpu-omap.c | 1 +
arch/arm/plat-omap/include/plat/clock.h | 2 +
6 files changed, 99 insertions(+), 42 deletions(-)
next reply other threads:[~2010-01-05 2:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 2:42 Paul Walmsley [this message]
2010-01-05 2:42 ` [PATCH 1/4] OMAP2: clock: clk2xxx.c doesn't compile if CPUFREQ is enabled Paul Walmsley
2010-01-05 10:51 ` Felipe Balbi
2010-01-05 16:03 ` Paul Walmsley
2010-01-05 2:42 ` [PATCH 2/4] OMAP2xxx OPP: clean up comments in OPP data Paul Walmsley
2010-01-05 2:42 ` [PATCH 3/4] OMAP2 clock: dynamically allocate CPUFreq frequency table Paul Walmsley
2010-01-05 10:42 ` Felipe Balbi
2010-01-05 16:22 ` Paul Walmsley
2010-01-05 2:42 ` [PATCH 4/4] OMAP clock/CPUFreq: avoid leaking the " Paul Walmsley
2010-01-05 10:46 ` Felipe Balbi
2010-01-05 15:58 ` Paul Walmsley
2010-01-19 19:26 ` Paul Walmsley
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=20100105024113.16275.96273.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-omap@vger.kernel.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