public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Richard Woodruff <r-woodruff2@ti.com>
Subject: Re: State of LDP3430 platform
Date: Mon, 6 Dec 2010 17:22:48 +0000	[thread overview]
Message-ID: <20101206172248.GA1000@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101206155959.GA8345@atomide.com>

On Mon, Dec 06, 2010 at 07:59:59AM -0800, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [101206 04:45]:
> >
> > ------------[ cut here ]------------
> > WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185 _omap_hwmod_enable+0x34/0x114()
> > omap_hwmod: wd_timer2: enabled state can only be entered from initialized, idle, or disabled state
> > Modules linked in:
> > ---[ end trace 1b75b31a2719ed1c ]---
> > wd_timer2: Could not enable clocks for omap2_disable_wdt
> 
> It seems like there's a problem handling a watchdog that's enabled
> in the bootloader.. But that's not the only problem, looks like I'm
> getting this on overo:
> 
> omap_device: omap_wdt.-1: new worst case activate latency 0: 122070
> OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
> omap_device: omap_wdt.-1: new worst case deactivate latency 0: 30517
> twl4030_wdt twl4030_wdt: Failed to register misc device
> twl4030_wdt: probe of twl4030_wdt failed with error -16

-16 = -EBUSY, which is probably because you have two watchdogs.  The
watchdog subsystem has one minor device number, so you can only have
one watchdog registered.

  reply	other threads:[~2010-12-06 17:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 12:55 State of LDP3430 platform Russell King - ARM Linux
2010-12-06 15:59 ` Tony Lindgren
2010-12-06 17:22   ` Russell King - ARM Linux [this message]
2010-12-06 18:02     ` Tony Lindgren
2010-12-06 18:19 ` Tony Lindgren
2010-12-06 18:27   ` Paul Walmsley
2010-12-07  8:37     ` Russell King - ARM Linux
2010-12-08  0:50       ` Paul Walmsley
2010-12-08  3:40         ` Paul Walmsley
2011-01-15  0:03           ` Tony Lindgren
2011-01-15 19:38             ` Paul Walmsley
2011-01-15 23:37               ` Russell King - ARM Linux
2011-01-16  0:04                 ` Russell King - ARM Linux
2011-01-16  0:05                 ` Woodruff, Richard
2011-01-16  0:30                   ` Russell King - ARM Linux
2011-01-16  1:09                   ` Paul Walmsley
2011-01-16  4:32                 ` Paul Walmsley
2011-01-16 15:08                   ` Thomas Weber
2011-01-18 19:36                     ` Paul Walmsley
2011-01-18 22:26                       ` [PATCH] omap1: Fix sched_clock for the MPU timer (Re: State of LDP3430 platform) Tony Lindgren
2011-01-18 22:35                         ` [PATCH] omap1: Fix booting for 15xx and 730 with omap1_defconfig " Tony Lindgren
2011-01-18 23:21                           ` Tony Lindgren
2011-01-19 18:43                             ` [PATCH] omap1: Fix sched_clock implementation when both MPU timer and 32K timer are used " Tony Lindgren
2011-01-19 18:44                         ` [PATCH] omap1: Fix sched_clock for the MPU timer " Tony Lindgren
2011-01-19 13:43                       ` State of LDP3430 platform Jarkko Nikula
2011-01-18  1:25                   ` Tony Lindgren
2011-01-18 19:24                     ` Paul Walmsley
2011-01-15 23:47             ` Woodruff, Richard
2011-01-17 17:34               ` Tony Lindgren
2011-01-17 17:44                 ` Woodruff, Richard
2011-02-12 16:02 ` Russell King - ARM Linux
2011-02-12 16:10   ` Russell King - ARM Linux
2011-02-23 22:50     ` Tony Lindgren
2011-02-23 23:22       ` Woodruff, Richard
2011-02-24  7:08         ` Rajendra Nayak
2011-02-24 13:07           ` Rajendra Nayak
2011-02-24  8:21       ` Janorkar, Mayuresh
2011-02-24  8:47         ` Russell King - ARM Linux

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=20101206172248.GA1000@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.com \
    /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