From: Paul Walmsley <paul@pwsan.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH 0/3] omap2 clock: create clock24xx.[ch] in preparation for 3430 clock code
Date: Wed, 12 Sep 2007 00:01:41 -0600 [thread overview]
Message-ID: <20070912060141.645853958@pwsan.com> (raw)
Hello,
this short patch series separates OMAP24xx clock definitions and code
from common clock code and headers. It's in preparation for OMAP3430
clock definitions and code.
All this happens in patches 2 and 3 of this series. The remaining
patch 1 moves some SDRC-related defines from clock.h into sdrc.h where
they belong.
The diffstat looks big, but the patches are mostly just cut and paste,
with a few minor changes to expose common functions to the linker, and
to satisfy checkpatch (at least somewhat).
Review and comments are appreciated, as always.
- Paul
diffstat:
arch/arm/mach-omap2/clock.c | 548 -----
arch/arm/mach-omap2/clock.h | 2661 -----------------------------
linux-omap/arch/arm/mach-omap2/Makefile | 3
linux-omap/arch/arm/mach-omap2/clock.c | 2
linux-omap/arch/arm/mach-omap2/clock.h | 62
linux-omap/arch/arm/mach-omap2/clock24xx.c | 521 +++++
linux-omap/arch/arm/mach-omap2/clock24xx.h | 2653 ++++++++++++++++++++++++++++
linux-omap/arch/arm/mach-omap2/sdrc.h | 31
8 files changed, 3290 insertions(+), 3191 deletions(-)
size:
text data bss dec hex filename
2853812 149804 85992 3089608 2f24c8 vmlinux.orig
2854244 149804 85992 3090040 2f2678 vmlinux
next reply other threads:[~2007-09-12 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 6:01 Paul Walmsley [this message]
2007-09-12 6:01 ` [PATCH 1/3] omap2 clock: move SDRC autorefresh counter defines into sdrc.h Paul Walmsley
2007-09-12 6:01 ` [PATCH 2/3] omap2 clock: move 24xx clock definitions from clock.h into clock24xx.h Paul Walmsley
2007-09-12 6:01 ` [PATCH 3/3] omap2 clock: move 24xx-specific clock code from clock.c into clock24xx.c Paul Walmsley
2007-09-17 18:16 ` [PATCH 0/3] omap2 clock: create clock24xx.[ch] in preparation for 3430 clock code Tony Lindgren
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=20070912060141.645853958@pwsan.com \
--to=paul@pwsan.com \
--cc=linux-omap-open-source@linux.omap.com \
/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