summaryrefslogtreecommitdiffstats
path: root/arch/arm64
diff options
context:
space:
mode:
authorJerome Brunet2018-04-27 13:31:51 +0200
committerMark Brown2018-05-01 22:56:36 +0200
commit40c57963789d451c26269e3bc9f9e803060fd9af (patch)
tree41b55350be7dd7d2d87bb6faa23c947f56c7a87d /arch/arm64
parentASoC: cirrus: i2s: Fix {TX|RX}LinCtrlData setup (diff)
downloadkernel-qcow2-linux-40c57963789d451c26269e3bc9f9e803060fd9af.tar.gz
kernel-qcow2-linux-40c57963789d451c26269e3bc9f9e803060fd9af.tar.xz
kernel-qcow2-linux-40c57963789d451c26269e3bc9f9e803060fd9af.zip
ASoC: dai playback and capture active may be greater than 1
At the moment playback_active and capture_active are using only 1 bit so the maximum active count is 1. However, snd_soc_runtime_activate() may be called several time on the same dai. This happens when a dai is part of several dai_links. It is often the case for "snd-soc-dummy-dai". This is a problem if snd_soc_runtime_activate() is called an even number of times on a dai. In this case the active count overflow back to 0. As consequence, ASoC functions, such as soc_dpcm_runtime_update(), won't run correctly. Storing these usage counts on plain 'unsigned int' solves the problem. Fixes: f0fba2ad1b6b ("ASoC: multi-component - ASoC Multi-Component Support") Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'arch/arm64')
0 files changed, 0 insertions, 0 deletions