From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Some OMAP clock/SCM patches for 2.6.34
Date: Mon, 11 Jan 2010 17:46:21 -0700 [thread overview]
Message-ID: <20100112004326.24684.91321.stgit@localhost.localdomain> (raw)
Hi,
these patches have been posted on the linux-omap mailing list and are
part of the planned queue for 2.6.34, but are being posted here in the event
that anyone else wishes to comment. These patches include clock support for
the Sitara platform (AM35xx) and some minor clock code improvements.
- Paul
---
Paul Walmsley (3):
OMAP3 clock: reorganize CK_* platform flags
OMAP clock: make the fixed divisor clock code available for all OMAPs
OMAP1 clock: convert armwdt_ck to use the fixed divisor recalc function
Ranjith Lohithakshan (2):
AM35xx: Add AM35xx specific control module registers
AM35xx: Clock table updates for AM3505/17
arch/arm/mach-omap1/clock.c | 6
arch/arm/mach-omap1/clock_data.c | 3
arch/arm/mach-omap2/clock.c | 11 -
arch/arm/mach-omap2/clock.h | 1
arch/arm/mach-omap2/clock2xxx_data.c | 4
arch/arm/mach-omap2/clock34xx_data.c | 365 +++++++++++++------------
arch/arm/plat-omap/clock.c | 11 +
arch/arm/plat-omap/include/plat/clkdev_omap.h | 26 +-
arch/arm/plat-omap/include/plat/clock.h | 3
arch/arm/plat-omap/include/plat/control.h | 17 +
10 files changed, 237 insertions(+), 210 deletions(-)
next reply other threads:[~2010-01-12 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 0:46 Paul Walmsley [this message]
2010-01-12 0:46 ` [PATCH 1/5] AM35xx: Add AM35xx specific control module registers Paul Walmsley
2010-01-12 0:46 ` [PATCH 2/5] OMAP3 clock: reorganize CK_* platform flags Paul Walmsley
2010-01-12 0:46 ` [PATCH 3/5] AM35xx: Clock table updates for AM3505/17 Paul Walmsley
2010-01-12 0:46 ` [PATCH 4/5] OMAP clock: make the fixed divisor clock code available for all OMAPs Paul Walmsley
2010-01-12 0:46 ` [PATCH 5/5] OMAP1 clock: convert armwdt_ck to use the fixed divisor recalc function 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=20100112004326.24684.91321.stgit@localhost.localdomain \
--to=paul@pwsan.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).