Re: State of LDP3430 platform

Russell King - ARM Linux
2010-12-06T17:22:58Z

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.