tree f3499a08a5f027fb77dfc214addb175289ed69cb
parent fb25621da5702c104ce0a48de5b174ced09e5b4e
author Takashi Iwai <tiwai@suse.de> 1642607568 +0100
committer Mark Brown <broonie@kernel.org> 1643385556 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmH0EtQACgkQJNaLcl1U
 h9ANSAf9Hgl+pPR+hHeS20MsEpJYB28Z4phj5XzCJfodZyyNoCx93yKPScqP5vrU
 mQt9gEk60EwUatKEVbdwogpLp4nPXnAqkmaizCinB9anl5opTcyGVsY9JBcG7zjL
 AvvohRikRKuHBGdtQjUmbm+dUobNF8iDbWfEXai6qe23PXR/5X0vBRWss/oJQV6f
 LlzvvjSon7oQahNvHG/JlGMHTrt7R5AaJYnTbn0DzUtxtQ86pilZlYSMnSUAQqz+
 W+wDlw4Kyr3KfkAFXICgiO9LZvSXxfw67MfnNV4zD/JpZvyPxSrc1LW3R56aRnuh
 8EEg0i4bG9rtXQcIhwhmxT4CfXQcew==
 =zpqe
 -----END PGP SIGNATURE-----

ASoC: soc-pcm: Fix DPCM lockdep warning due to nested stream locks

The recent change for DPCM locking caused spurious lockdep warnings.
Actually the warnings are false-positive, as those are triggered due
to the nested stream locks for FE and BE.  Since both locks belong to
the same lock class, lockdep sees it as if a deadlock.

For fixing this, we need to take PCM stream locks for BE with the
nested lock primitives.  Since currently snd_pcm_stream_lock*() helper
assumes only the top-level single locking, a new helper function
snd_pcm_stream_lock_irqsave_nested() is defined for a single-depth
nested lock, which is now used in the BE DAI trigger that is always
performed inside a FE stream lock.

Fixes: b2ae80663008 ("ASoC: soc-pcm: serialize BE triggers")
Reported-and-tested-by: Hans de Goede <hdegoede@redhat.com>
Reported-and-tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
Link: https://lore.kernel.org/r/73018f3c-9769-72ea-0325-b3f8e2381e30@redhat.com
Link: https://lore.kernel.org/alsa-devel/9a0abddd-49e9-872d-2f00-a1697340f786@samsung.com
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Link: https://lore.kernel.org/r/20220119155249.26754-2-tiwai@suse.de
Signed-off-by: Mark Brown <broonie@kernel.org>