tree f02036e66d52fca3926d239cbb7cb2e8fd865052
parent 8938f75a5e35c597a647c28984a0304da7a33d63
author Vijendar Mukunda <Vijendar.Mukunda@amd.com> 1685014195 +0530
committer Mark Brown <broonie@kernel.org> 1685450607 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmR1728ACgkQJNaLcl1U
 h9CGfQf/WUvWdok5ufSXunXeyRtL0KDoDy9mr6rUzFydsnQBjWKqvyZq6s2RmSVj
 lMkWlNq9Z5xJQE4IJrvNtMEIrNs9tgaj/aJLFagwqa2tZ+Olucv04vWC/k0Vfh7o
 43s9L58H2dTXqeDIkQpSoK+kbmat3Zjuz3V76vwQTGeGWyxreCQSj4epBcoTcC7a
 lFVxwyYC2RxM0PP3hp0yrawKA3xPx8noBJewWFKg783t7ccZjGvFDIltozMlAYhg
 qccXf8EFASg4BKWQrCJNIPTnPX57LsqY8KPtyU7W7UM5N4iEZkW63xoKXmL/G+0x
 5tFtMTnjfoBEOz3GG+th+oniApCs+Q==
 =X3c5
 -----END PGP SIGNATURE-----

ASoC: amd: ps: fix for acp_lock access in pdm driver

Sending the mutex address(acp_lock) as platform
data during ACP PDM platform driver register sequence,
its creating copy of the platform data.
Referencing this platform data in ACP PDM driver results
incorrect reference to the common lock usage.

Instead of directly passing the lock address as platform
data, retrieve it from parent driver data structure
and use the same lock reference in ACP PDM driver.

Fixes: 45aa83cb9388 ("ASoC: amd: ps: use acp_lock to protect common registers in pdm driver")

Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Link: https://lore.kernel.org/r/20230525113000.1290758-1-Vijendar.Mukunda@amd.com
Signed-off-by: Mark Brown <broonie@kernel.org>