From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Clockdomain split series
Date: Tue, 25 Jan 2011 17:21:43 +0530 [thread overview]
Message-ID: <1295956308-23860-1-git-send-email-rnayak@ti.com> (raw)
This patch series is an effort to split the clockdomain
framework into platform independent and platform specific parts
as was done for the powerdomain framework.
This certainlly helps remove the various cpu_is_* checks
which exist today in the framework and makes
the code more maintainable and readable.
The series is boot tested on OMAP2430/3430/4430SDP platforms.
Also on OMAP3430SDP, OFF mode in suspend path is validated
using the omap3_pm_defconfig.
This series is based on mainline 2.6.38-rc2 and
can be found here
git://gitorious.org/omap-pm/linux.git clockdomain-split-v2-rc2
Version History
---------------
v2
-1- removed wrongly populated sleepdep support for OMAP2
-2- Fixed error handling in apis
For a wider review, posting this series with
linux-arm-kernel list copied.
This version has no functional diff with the
earlier one posted here
http://www.mail-archive.com/linux-omap at vger.kernel.org/msg42570.html
Rajendra Nayak (5):
OMAP: clockdomain: Infrastructure to put arch specific code
OMAP: clockdomain: Arch specific funcs to handle deps
OMAP: clockdomain: Arch specific funcs for sleep/wakeup of clkdm
OMAP: clockdomain: Arch specific funcs for hwsup control of clkdm
OMAP: clockdomain: Arch specific funcs for clkdm_clk_enable/disable
arch/arm/mach-omap2/Makefile | 3 +
arch/arm/mach-omap2/clock.c | 6 +-
arch/arm/mach-omap2/clockdomain.c | 410 +++++++---------------
arch/arm/mach-omap2/clockdomain.h | 58 +++-
arch/arm/mach-omap2/clockdomain2xxx_3xxx.c | 270 ++++++++++++++
arch/arm/mach-omap2/clockdomain44xx.c | 77 ++++
arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.c | 9 +-
arch/arm/mach-omap2/clockdomains44xx_data.c | 2 +-
arch/arm/mach-omap2/cpuidle34xx.c | 4 +-
arch/arm/mach-omap2/io.c | 6 +-
arch/arm/mach-omap2/pm.c | 6 +-
arch/arm/mach-omap2/pm24xx.c | 8 +-
arch/arm/mach-omap2/pm34xx.c | 6 +-
13 files changed, 557 insertions(+), 308 deletions(-)
create mode 100644 arch/arm/mach-omap2/clockdomain2xxx_3xxx.c
create mode 100644 arch/arm/mach-omap2/clockdomain44xx.c
next reply other threads:[~2011-01-25 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 11:51 Rajendra Nayak [this message]
2011-01-25 11:51 ` [PATCH v2 1/5] OMAP: clockdomain: Infrastructure to put arch specific code Rajendra Nayak
2011-01-25 11:51 ` [PATCH v2 2/5] OMAP: clockdomain: Arch specific funcs to handle deps Rajendra Nayak
2011-01-25 11:51 ` [PATCH v2 3/5] OMAP: clockdomain: Arch specific funcs for sleep/wakeup of clkdm Rajendra Nayak
2011-01-25 11:51 ` [PATCH v2 4/5] OMAP: clockdomain: Arch specific funcs for hwsup control " Rajendra Nayak
2011-01-25 11:51 ` [PATCH v2 5/5] OMAP: clockdomain: Arch specific funcs for clkdm_clk_enable/disable Rajendra Nayak
2011-02-11 2:03 ` [PATCH v2 2/5] OMAP: clockdomain: Arch specific funcs to handle deps Paul Walmsley
2011-02-11 2:10 ` Paul Walmsley
2011-02-11 4:11 ` Rajendra Nayak
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=1295956308-23860-1-git-send-email-rnayak@ti.com \
--to=rnayak@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).