From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/9] OMAP2+: hwmod/clockevent: allow hwmods to be set up individually
Date: Mon, 28 Feb 2011 14:12:02 -0700 [thread overview]
Message-ID: <20110228210858.15286.3200.stgit@twilight.localdomain> (raw)
Hello,
This series adds the ability to set up (formerly known
as "late-initialize") individual hwmods, rather than doing them
all at once. The goal here is for clockevent (and eventually
clocksource) hwmods to be set up right before they are needed, in
the timer init code. Then omap_hwmod_setup_all(), which
sets up the rest of the hwmods, is intended to run as an
initcall -- much later in the boot process.
This series includes the OMAP2/3 hwmod data for the GPTIMERs that
Tarun posted earlier. This data is necessary for this new code
to avoid warnings during boot.
Boot-tested on OMAP34xx Beagleboard and OMAP4430ES2 Panda.
Applies on Tony's 7cab8713b1ed0dab08ad6458f92a40b7ff4be619
("Merge branch 'for-tony' of
git://gitorious.org/linux-omap-dss2/linux into omap-for-linus")
- Paul
---
hwmod_clockevent_2.6.39
text data bss dec hex filename
5781261 484056 5598712 11864029 b507dd vmlinux.omap2plus_defconfig.orig
5785233 491096 5598680 11875009 b532c1 vmlinux.omap2plus_defconfig
Paul Walmsley (6):
OMAP2+: hwmod: allow multiple calls to omap_hwmod_init()
OMAP2+: hwmod: rename some init functions
OMAP2+: hwmod: find MPU initiator hwmod during in _register()
OMAP2+: hwmod: ignore attempts to re-setup a hwmod
OMAP2+: hwmod: add ability to setup individual hwmods
OMAP2+: clockevent: set up GPTIMER clockevent hwmod right before timer init
Thara Gopinath (3):
OMAP2420: hwmod data: add dmtimer
OMAP2430: hwmod data: add dmtimer
OMAP3: hwmod data: add dmtimer
arch/arm/mach-omap2/omap_hwmod.c | 154 ++++--
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 636 +++++++++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 635 +++++++++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 651 ++++++++++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 2
arch/arm/mach-omap2/serial.c | 2
arch/arm/mach-omap2/timer-gp.c | 7
arch/arm/plat-omap/include/plat/dmtimer.h | 11
arch/arm/plat-omap/include/plat/omap_hwmod.h | 9
9 files changed, 2045 insertions(+), 62 deletions(-)
next reply other threads:[~2011-02-28 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 21:12 Paul Walmsley [this message]
2011-02-28 21:12 ` [PATCH v2 1/9] OMAP2420: hwmod data: add dmtimer Paul Walmsley
2011-02-28 21:12 ` [PATCH v2 2/9] OMAP2430: " Paul Walmsley
2011-02-28 21:12 ` [PATCH v2 3/9] OMAP3: " Paul Walmsley
2011-02-28 21:12 ` [PATCH v2 4/9] OMAP2+: hwmod: allow multiple calls to omap_hwmod_init() Paul Walmsley
2011-02-28 21:12 ` [PATCH v2 5/9] OMAP2+: hwmod: rename some init functions Paul Walmsley
2011-03-01 6:53 ` DebBarma, Tarun Kanti
2011-02-28 21:12 ` [PATCH v2 6/9] OMAP2+: hwmod: find MPU initiator hwmod during in _register() Paul Walmsley
2011-02-28 21:12 ` [PATCH v2 7/9] OMAP2+: hwmod: ignore attempts to re-setup a hwmod Paul Walmsley
2011-02-28 21:12 ` [PATCH v2 8/9] OMAP2+: hwmod: add ability to setup individual hwmods Paul Walmsley
2011-02-28 21:12 ` [PATCH v2 9/9] OMAP2+: clockevent: set up GPTIMER clockevent hwmod right before timer init 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=20110228210858.15286.3200.stgit@twilight.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).