From: santosh.shilimkar@ti•com (Santosh Shilimkar)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] OMAP4: clockdomain: Follow recommended enable sequence
Date: Thu, 21 Apr 2011 10:17:32 +0530 [thread overview]
Message-ID: <4DAFB6E4.3080304@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104201340450.5985@utopia.booyaka.com>
On 4/21/2011 1:12 AM, Paul Walmsley wrote:
>
> Hi Rajendra, Santosh,
>
> just FYI I just observed this happening without the clockdomain patch, and
> tracked this down. It seems that there is an intermittent
> problem with the OMAP L3 bus code. On the 35xx BeagleBoard here, it
> occasionally hangs after powerup:
>
> [ 0.810119] OMAP GPIO hardware version 2.5
> [ 0.815368] OMAP GPIO hardware version 2.5
> [ 0.820465] OMAP GPIO hardware version 2.5
> [ 0.825531] OMAP GPIO hardware version 2.5
> [ 0.830657] OMAP GPIO hardware version 2.5
> [ 0.835784] OMAP GPIO hardware version 2.5
> [ 0.840881] initcall omap_gpio_drv_reg+0x0/0xc returned 0 after 38146
> usecs
> [ 0.848358] calling bdi_class_init+0x0/0x50 @ 1
> [ 0.854003] initcall bdi_class_init+0x0/0x50 returned 0 after 0 usecs
> [ 0.860870] calling kobject_uevent_init+0x0/0x20 @ 1
> [ 0.866363] initcall kobject_uevent_init+0x0/0x20 returned 0 after 0
> usecs
> [ 0.873626] calling gpiolib_sysfs_init+0x0/0x98 @ 1
> [ 0.885894] initcall gpiolib_sysfs_init+0x0/0x98 returned 0 after 0
> usecs
> [ 0.893157] calling lcd_class_init+0x0/0x58 @ 1
> [ 0.898742] initcall lcd_class_init+0x0/0x58 returned 0 after 0 usecs
> [ 0.905731] calling backlight_class_init+0x0/0x70 @ 1
> [ 0.911834] initcall backlight_class_init+0x0/0x70 returned 0 after 0
> usecs
> [ 0.919219] calling tty_class_init+0x0/0x3c @ 1
> [ 0.924743] initcall tty_class_init+0x0/0x3c returned 0 after 0 usecs
> [ 0.931610] calling vtconsole_class_init+0x0/0xe4 @ 1
> [ 0.938812] initcall vtconsole_class_init+0x0/0xe4 returned 0 after
> 7629 usecs
> [ 0.946472] calling wakeup_sources_debugfs_init+0x0/0x3c @ 1
> [ 0.952606] initcall wakeup_sources_debugfs_init+0x0/0x3c returned 0
> after 0 usecs
> [ 0.960571] calling spi_init+0x0/0x88 @ 1
> [ 0.966247] initcall spi_init+0x0/0x88 returned 0 after 0 usecs
> [ 0.972564] calling i2c_init+0x0/0x70 @ 1
> [ 0.978485] initcall i2c_init+0x0/0x70 returned 0 after 0 usecs
> [ 0.984832] calling omap3_l3_init+0x0/0x14 @ 1
>
Will have a look at it
prev parent reply other threads:[~2011-04-21 4:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 13:25 [PATCH] OMAP4: clockdomain: Follow recommended enable sequence Rajendra Nayak
2011-03-09 3:50 ` Paul Walmsley
2011-03-09 10:19 ` Rajendra Nayak
2011-03-09 16:28 ` Kevin Hilman
2011-03-09 21:44 ` Paul Walmsley
2011-03-10 12:18 ` Paul Walmsley
2011-03-10 12:58 ` Rajendra Nayak
2011-03-10 13:16 ` Paul Walmsley
2011-03-10 13:17 ` Paul Walmsley
2011-03-10 13:34 ` Ben Dooks
2011-03-10 13:36 ` Paul Walmsley
2011-03-10 14:39 ` Paul Walmsley
2011-03-11 13:26 ` Rajendra Nayak
2011-03-11 16:47 ` Kevin Hilman
2011-03-12 7:53 ` Rajendra Nayak
2011-03-14 10:58 ` Rajendra Nayak
2011-03-21 8:51 ` Rajendra Nayak
2011-03-28 17:04 ` Paul Walmsley
2011-03-29 6:55 ` Rajendra Nayak
2011-04-01 14:51 ` Rajendra Nayak
2011-04-01 15:40 ` Rajendra Nayak
2011-04-04 6:47 ` Paul Walmsley
2011-04-04 6:57 ` Santosh Shilimkar
2011-04-05 12:47 ` Rajendra Nayak
2011-03-23 23:29 ` Paul Walmsley
2011-04-20 19:42 ` Paul Walmsley
2011-04-21 4:47 ` Santosh Shilimkar [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=4DAFB6E4.3080304@ti.com \
--to=santosh.shilimkar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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