From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] ARM: OMAP2+: hwmod/timer: first set of cleanups for 3.4
Date: Mon, 27 Feb 2012 22:36:43 -0700 [thread overview]
Message-ID: <20120228053524.16278.59430.stgit@dusk> (raw)
Hi
This series does some cleanup and documentation on the OMAP hwmod code
(and a bit of the OMAP4 data) and timer code. It is the first
prerequisite series to removing a big chunk of hwmod data -- that
will be done in a later series. This second version reimplements
the hardreset code in a way that will hopefully fix some of the
issues that Kevin was seeing.
Boot-tested on an OMAP35xx BeagleBoard and OMAP44xx ES2 Pandaboard.
This series is also available via git from git://git.pwsan.com/linux-2.6 in
the branch "hwmod_code_cleanup_3.4".
- Paul
---
hwmod_code_cleanup_3.4
text data bss dec hex filename
6600418 680476 5593820 12874714 c473da vmlinux.omap2plus_defconfig.orig
6600374 679788 5593820 12873982 c470fe vmlinux.omap2plus_defconfig
Paul Walmsley (8):
ARM: OMAP2+: hwmod: control all hardreset lines attached to a hwmod
ARM: OMAP4: hwmod data: remove pseudo-hwmods associated with hardreset lines
ARM: OMAP2+: hwmod: reorganize and document the setup process
ARM: OMAP2+: hwmod: revise hardreset behavior
ARM: OMAP2+: hwmod: ensure that SYSCONFIG bits are reprogrammed after a reset
ARM: OMAP2+: hwmod: provide a function to return the address space of the MPU RT
ARM: OMAP2+: hwmod: add omap_hwmod_get_resource_byname()
ARM: OMAP2+: timer: use a proper interface to get hwmod data
arch/arm/mach-omap2/omap_hwmod.c | 671 +++++++++++++++++++-------
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 101 ----
arch/arm/mach-omap2/timer.c | 15 -
arch/arm/plat-omap/include/plat/omap_hwmod.h | 2
4 files changed, 520 insertions(+), 269 deletions(-)
next reply other threads:[~2012-02-28 5:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 5:36 Paul Walmsley [this message]
2012-02-28 5:36 ` [PATCH v2 1/8] ARM: OMAP2+: hwmod: control all hardreset lines attached to a hwmod Paul Walmsley
2012-02-28 5:36 ` [PATCH v2 2/8] ARM: OMAP4: hwmod data: remove pseudo-hwmods associated with hardreset lines Paul Walmsley
2012-02-28 5:36 ` [PATCH v2 3/8] ARM: OMAP2+: hwmod: reorganize and document the setup process Paul Walmsley
2012-04-19 8:14 ` Paul Walmsley
2012-04-19 8:17 ` Paul Walmsley
2012-04-19 8:22 ` Cousson, Benoit
2012-04-19 9:49 ` Paul Walmsley
2012-04-19 12:05 ` Cousson, Benoit
2012-02-28 5:36 ` [PATCH v2 4/8] ARM: OMAP2+: hwmod: revise hardreset behavior Paul Walmsley
2012-04-19 6:53 ` Paul Walmsley
2012-04-19 12:07 ` Cousson, Benoit
2012-04-19 17:17 ` Paul Walmsley
2012-04-19 19:14 ` Cousson, Benoit
2012-04-19 19:46 ` Paul Walmsley
2012-04-19 21:15 ` Ramirez Luna, Omar
2012-02-28 5:37 ` [PATCH v2 5/8] ARM: OMAP2+: hwmod: ensure that SYSCONFIG bits are reprogrammed after a reset Paul Walmsley
2012-03-15 0:31 ` Ramirez Luna, Omar
2012-03-15 6:25 ` Paul Walmsley
2012-03-15 15:21 ` Ramirez Luna, Omar
2012-04-11 20:15 ` Paul Walmsley
2012-04-19 8:21 ` Paul Walmsley
2012-02-28 5:37 ` [PATCH v2 6/8] ARM: OMAP2+: hwmod: provide a function to return the address space of the MPU RT Paul Walmsley
2012-02-28 5:37 ` [PATCH v2 7/8] ARM: OMAP2+: hwmod: add omap_hwmod_get_resource_byname() Paul Walmsley
2012-02-28 5:37 ` [PATCH v2 8/8] ARM: OMAP2+: timer: use a proper interface to get hwmod data 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=20120228053524.16278.59430.stgit@dusk \
--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).