From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] OMAP2: clockdomain/powerdomain: remove OMAP_CHIP bitmasks
Date: Thu, 01 Sep 2011 20:19:11 -0600 [thread overview]
Message-ID: <20110902021321.8185.63172.stgit@dusk> (raw)
Remove the OMAP_CHIP bitmasks from the powerdomain and clockdomain
code. In their place, use lists of powerdomains and clockdomains to
register for particular chips and chip families.
The intention of this change is to reduce the number of lines that
need to be patched to add support for new SoCs that are similar to
previous SoCs.
This series has been boot-tested on a 2430SDP, BeagleBoard 35xx and
37xx, and PandaBoard 44xxES2, but I don't have boards for all of the
different variants needed for a complete test.
A git branch is available at git://git.pwsan.com/linux-2.6 based on
v3.1-rc4 with prcm-fixes-a-3.1rc.
- Paul
---
pwrdm_clkdm_remove_omap_chip_cleanup_3.2
text data bss dec hex filename
6330180 656956 5591124 12578260 bfedd4 vmlinux.omap2plus_defconfig.orig
6330432 656052 5591124 12577608 bfeb48 vmlinux.omap2plus_defconfig
Paul Walmsley (4):
OMAP: clockdomain: split clkdm_init()
OMAP: clockdomain code/data: remove omap_chip bitmask from struct clockdomain
OMAP: powerdomain: split pwrdm_init() into two functions
OMAP: powerdomain: remove omap_chip bitmasks
arch/arm/mach-omap2/Makefile | 5
arch/arm/mach-omap2/clockdomain.c | 149 +++-
arch/arm/mach-omap2/clockdomain.h | 22 -
arch/arm/mach-omap2/clockdomain2xxx_3xxx.c | 4
arch/arm/mach-omap2/clockdomain44xx.c | 2
arch/arm/mach-omap2/clockdomains2420_data.c | 155 ++++
arch/arm/mach-omap2/clockdomains2430_data.c | 181 +++++
arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.c | 803 ----------------------
arch/arm/mach-omap2/clockdomains3xxx_data.c | 398 +++++++++++
arch/arm/mach-omap2/clockdomains44xx_data.c | 409 ++---------
arch/arm/mach-omap2/io.c | 8
arch/arm/mach-omap2/powerdomain-common.c | 7
arch/arm/mach-omap2/powerdomain.c | 87 ++
arch/arm/mach-omap2/powerdomain.h | 9
arch/arm/mach-omap2/powerdomains2xxx_3xxx_data.c | 19 -
arch/arm/mach-omap2/powerdomains2xxx_data.c | 44 +
arch/arm/mach-omap2/powerdomains3xxx_data.c | 81 +-
arch/arm/mach-omap2/powerdomains44xx_data.c | 20 -
18 files changed, 1104 insertions(+), 1299 deletions(-)
create mode 100644 arch/arm/mach-omap2/clockdomains2420_data.c
create mode 100644 arch/arm/mach-omap2/clockdomains2430_data.c
create mode 100644 arch/arm/mach-omap2/clockdomains3xxx_data.c
next reply other threads:[~2011-09-02 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 2:19 Paul Walmsley [this message]
2011-09-02 2:19 ` [PATCH 1/4] OMAP: clockdomain: split clkdm_init() Paul Walmsley
2011-09-02 2:19 ` [PATCH 2/4] OMAP: clockdomain code/data: remove omap_chip bitmask from struct clockdomain Paul Walmsley
2011-09-05 1:41 ` Paul Walmsley
2011-09-02 2:19 ` [PATCH 3/4] OMAP: powerdomain: split pwrdm_init() into two functions Paul Walmsley
2011-09-02 2:19 ` [PATCH 4/4] OMAP: powerdomain: remove omap_chip bitmasks Paul Walmsley
2011-09-05 1:50 ` Paul Walmsley
2011-09-02 12:33 ` [PATCH 0/4] OMAP2: clockdomain/powerdomain: remove OMAP_CHIP bitmasks 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=20110902021321.8185.63172.stgit@dusk \
--to=paul@pwsan.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).