aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/sound/soc/ux500
diff options
context:
space:
mode:
authorJohan Hovold <johan@kernel.org>2017-07-12 17:55:29 +0200
committerMark Brown <broonie@kernel.org>2017-07-17 15:50:32 +0100
commitc641e5b207ed7dfaa692820aeb5b6dde3de3e9b0 (patch)
tree32db6d91738de6ae0b00b6816068eb0ad109faae /sound/soc/ux500
parentLinux v4.13-rc1 (diff)
downloadwireguard-linux-c641e5b207ed7dfaa692820aeb5b6dde3de3e9b0.tar.xz
wireguard-linux-c641e5b207ed7dfaa692820aeb5b6dde3de3e9b0.zip
ASoC: fix pcm-creation regression
This reverts commit 99b04f4c4051 ("ASoC: add Component level pcm_new/pcm_free"), which started calling the pcm_new callback for every component in a *card* when creating a new pcm, something which does not seem to make any sense. This specifically led to memory leaks in systems with more than one platform component and where DMA memory is allocated in the platform-driver callback. For example, when both mcasp devices are being used on an am335x board, DMA memory would be allocated twice for every DAI link during probe. When CONFIG_SND_VERBOSE_PROCFS was set this fortunately also led to warnings such as: WARNING: CPU: 0 PID: 565 at ../fs/proc/generic.c:346 proc_register+0x110/0x154 proc_dir_entry 'sub0/prealloc' already registered Since there seems to be no users of the new component callbacks, and the current implementation introduced a regression, let's revert the offending commit for now. Fixes: 99b04f4c4051 ("ASoC: add Component level pcm_new/pcm_free") Signed-off-by: Johan Hovold <johan@kernel.org> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Tested-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Mark Brown <broonie@kernel.org> Cc: stable <stable@vger.kernel.org> # 4.10
Diffstat (limited to 'sound/soc/ux500')
0 files changed, 0 insertions, 0 deletions