From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] OMAP2+: hwmod/clockevent: allow late-init of individual hwmods
Date: Wed, 23 Feb 2011 15:28:40 +0100 [thread overview]
Message-ID: <4D651998.3040002@ti.com> (raw)
In-Reply-To: <20110223070455.5874.51326.stgit@twilight.localdomain>
Hi Paul,
On 2/23/2011 8:11 AM, Paul Walmsley wrote:
> Hello,
>
> This series adds the ability to late-initialize individual
> hwmods. The goal here is for clockevent (and eventually
> clocksource) hwmods to be late-initialized individually, and
> right before they are needed, in the timer init code. Then
> omap_hwmod_late_init(), which late-inits 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 N800, OMAP34xx Beagleboard and OMAP4430ES2 Panda.
I'm testing it on 4430sdp, and I have the following warning:
[ 0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck.
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: at arch/arm/mach-omap2/timer-gp.c:157 omap2_gp_timer_init+0x80/0x190()
[ 0.000000] timer-gp: omap_dm_timer_set_source() failed
[ 0.000000] Modules linked in:
[ 0.000000] [<c0062a6c>] (unwind_backtrace+0x0/0xec) from [<c009422c>] (warn_slowpath_common+0x4c/0x64)
[ 0.000000] [<c009422c>] (warn_slowpath_common+0x4c/0x64) from [<c00942c4>] (warn_slowpath_fmt+0x2c/0x3c)
[ 0.000000] [<c00942c4>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0010e30>] (omap2_gp_timer_init+0x80/0x190)
[ 0.000000] [<c0010e30>] (omap2_gp_timer_init+0x80/0x190) from [<c000c0dc>] (time_init+0x20/0x30)
[ 0.000000] [<c000c0dc>] (time_init+0x20/0x30) from [<c0008cbc>] (start_kernel+0x1a4/0x30c)
[ 0.000000] [<c0008cbc>] (start_kernel+0x1a4/0x30c) from [<80008038>] (0x80008038)
[ 0.000000] ---[ end trace 1b75b31a2719ed1c ]---
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
Regards,
Benoit
next prev parent reply other threads:[~2011-02-23 14:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 7:11 [PATCH 0/8] OMAP2+: hwmod/clockevent: allow late-init of individual hwmods Paul Walmsley
2011-02-23 7:11 ` [PATCH 1/8] OMAP2420: hwmod data: add dmtimer Paul Walmsley
2011-02-23 7:11 ` [PATCH 2/8] OMAP2430: " Paul Walmsley
2011-02-23 7:11 ` [PATCH 3/8] OMAP3: " Paul Walmsley
2011-02-23 7:11 ` [PATCH 4/8] OMAP2+: hwmod: find MPU initiator hwmod during in _register() Paul Walmsley
2011-02-23 14:38 ` Cousson, Benoit
2011-02-24 9:16 ` Paul Walmsley
2011-02-23 7:11 ` [PATCH 5/8] OMAP2+: hwmod: allow multiple calls to omap_hwmod_init() Paul Walmsley
2011-02-23 14:46 ` Cousson, Benoit
2011-02-23 7:11 ` [PATCH 6/8] OMAP2+: hwmod: ignore attempts to re-late-init a hwmod Paul Walmsley
2011-02-23 7:11 ` [PATCH 7/8] OMAP2+: hwmod: add ability to late-init individual hwmods Paul Walmsley
2011-02-23 19:12 ` Tony Lindgren
2011-02-24 9:06 ` Paul Walmsley
2011-02-23 7:11 ` [PATCH 8/8] OMAP2+: clockevent: late-init GPTIMER clockevent hwmod right before timer init Paul Walmsley
2011-02-23 8:53 ` [PATCH 8/8] OMAP2+: clockevent: late-init GPTIMER clockevent hwmodright " Santosh Shilimkar
2011-02-23 11:48 ` DebBarma, Tarun Kanti
2011-02-24 8:13 ` Paul Walmsley
2011-02-24 8:15 ` Paul Walmsley
2011-02-24 8:29 ` DebBarma, Tarun Kanti
2011-02-24 9:00 ` Paul Walmsley
2011-02-24 15:41 ` Tony Lindgren
2011-02-25 14:07 ` DebBarma, Tarun Kanti
2011-02-24 8:57 ` Santosh Shilimkar
2011-02-23 9:13 ` [PATCH 8/8] OMAP2+: clockevent: late-init GPTIMER clockevent hwmod right " DebBarma, Tarun Kanti
2011-02-24 8:18 ` Paul Walmsley
2011-02-23 14:28 ` Cousson, Benoit [this message]
2011-02-28 2:31 ` [PATCH 0/8] OMAP2+: hwmod/clockevent: allow late-init of individual hwmods Paul Walmsley
2011-02-28 11:17 ` Cousson, Benoit
2011-03-02 17:54 ` Tony Lindgren
2011-03-03 11:10 ` Cousson, Benoit
2011-03-04 14:51 ` Cousson, Benoit
2011-03-04 16:19 ` Tony Lindgren
2011-03-04 16:39 ` Cousson, Benoit
2011-03-04 16:42 ` Paul Walmsley
2011-03-04 16:48 ` Santosh Shilimkar
2011-02-23 19:12 ` 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=4D651998.3040002@ti.com \
--to=b-cousson@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).