summaryrefslogtreecommitdiffstats
path: root/sound/soc/codecs/ssm2602.c
diff options
context:
space:
mode:
authorOskar Schirmer <oskar@scara.com>2013-11-12 15:46:38 +0000
committerMark Brown <broonie@linaro.org>2013-11-14 12:59:44 +0000
commitfc7dc61d9a87011aaf8a6eb3144ebf9552adf5d2 (patch)
tree4d6e4007b7fd6bd144fadd4ef01390728304876d /sound/soc/codecs/ssm2602.c
parent71d0c3a876e007f68fc2ed433119dd4f4dc408a7 (diff)
ASoC: fsl: imx-pcm-fiq: omit fiq counter to avoid harm in unbalanced situations
Unbalanced calls to snd_imx_pcm_trigger() may result in endless FIQ activity and thus provoke eternal sound. While on the first glance, the switch statement looks pretty symmetric, the SUSPEND/RESUME pair is not: the suspend case comes along snd_pcm_suspend_all(), which for fsl/imx-pcm-fiq is called only at snd_soc_suspend(), but the resume case originates straight from the SNDRV_PCM_IOCTL_RESUME. This way userland may provoke an unbalanced resume, which might cause the fiq_enable counter to increase and never return to zero again, so eventually imx_pcm_fiq is never disabled. Simply removing the fiq_enable will solve the problem, as long as one never goes play and capture game simultaneously, but beware trying both at once, the early TRIGGER_STOP will cut off the other activity prematurely. So now playing and capturing is scrutinized separately, instead of by counting. Signed-off-by: Oskar Schirmer <oskar@scara.com> Signed-off-by: Mark Brown <broonie@linaro.org> Cc: stable@vger.kernel.org
Diffstat (limited to 'sound/soc/codecs/ssm2602.c')
0 files changed, 0 insertions, 0 deletions