Hi David,
On Fri, 3 Oct 2008, David Brownell wrote:
> On Tuesday 16 September 2008, Felipe Contreras wrote:
> > This is exactly the same as the overo configuration. It might make sense
> > to have them in a single one.
>
> I got a hard lockup (no timer ticking), no blinkenlights, etc ...
> doesn't look like the issue is *this* driver.
...
> [ INFO: possible recursive locking detected ]
> 2.6.27-rc8-omap1 #174
> ---------------------------------------------
> aplay/1816 is trying to acquire lock:
> (clockfw_lock){....}, at: [<c0036be4>] clk_enable+0x24/0x70
>
> but task is already holding lock:
> (clockfw_lock){....}, at: [<c0036be4>] clk_enable+0x24/0x70
Yeah, the code that's in that driver is broken. The driver
sets up a custom clk_enable() function that calls clk_enable() again. And
clk_enable() takes clockfw_lock.
The omap_clk_associate() code should resolve this problem.
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
