[alsa-devel] [PATCH 2/2] ASoC: DAPM - Make sure DAPM widget IO ops hold the component mutex.

Mark Brown broonie at opensource.wolfsonmicro.com
Sun Mar 11 13:55:59 CET 2012

On Fri, Mar 09, 2012 at 01:11:26PM -0600, Timur Tabi wrote:
> Liam Girdwood wrote:

> > Can you switch on the mutex debugging kernel config here.  I've just had
> > a quick look and the WM8776 and its not holding the codec mutex or
> > calling snd_soc_update_bits_locked() so it must deadlock via another
> > path.

> Enabling the debug options didn't reveal anything, unfortunately.

The major difference between your two boards is that CS4270 doesn't use
DAPM while WM8776 does.  Though if one of them were going to break I'd
really expect it to be the CS4270, obviously non-DAPM CODECs are a real
corner case (to the point where I think you're the only active user of
such a device) and certainly all Liam's TI reference systems have DAPM
CODECs so this is really surprising...  I wonder if PowerPC mutexes are
less forgiving here?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20120311/7dae4269/attachment.sig 

More information about the Alsa-devel mailing list