From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] OMAP2: clockdomain/powerdomain: remove OMAP_CHIP bitmasks
Date: Fri, 2 Sep 2011 15:33:29 +0300 [thread overview]
Message-ID: <20110902123328.GW3548@atomide.com> (raw)
In-Reply-To: <20110902021321.8185.63172.stgit@dusk>
* Paul Walmsley <paul@pwsan.com> [110902 04:58]:
> 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.
Great! Thanks for working on this. Let's get this tested and merged
into our cleanup branch ASAP as this will simplify adding new omaps
quite a bit :)
Tony
prev parent reply other threads:[~2011-09-02 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 2:19 [PATCH 0/4] OMAP2: clockdomain/powerdomain: remove OMAP_CHIP bitmasks Paul Walmsley
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 ` Tony Lindgren [this message]
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=20110902123328.GW3548@atomide.com \
--to=tony@atomide.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).