summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorKuninori Morimoto <kuninori.morimoto.gx@renesas.com>2019-02-01 16:49:30 +0900
committerMark Brown <broonie@kernel.org>2019-02-02 15:41:29 +0000
commit7aea8a9d71d54f449f49e20324df06341cc18395 (patch)
tree7af6a24dd84a90576bdadb24ec7feae06615f964 /README
parentd0b95e6cd298a785c126e75a085af6dd7b7b1f60 (diff)
downloadlinux-7aea8a9d71d54f449f49e20324df06341cc18395.tar.gz
linux-7aea8a9d71d54f449f49e20324df06341cc18395.tar.bz2
linux-7aea8a9d71d54f449f49e20324df06341cc18395.zip
ASoC: rsnd: fixup MIX kctrl registration
Renesas sound device has many IPs and many situations. If platform/board uses MIXer, situation will be more complex. To avoid duplicate DVC kctrl registration when MIXer was used, it had original flags. But it was issue when sound card was re-binded, because no one can't cleanup this flags then. To solve this issue, commit 9c698e8481a15237a ("ASoC: rsnd: tidyup registering method for rsnd_kctrl_new()") checks registered card->controls, because if card was re-binded, these were cleanuped automatically. This patch could solve re-binding issue. But, it start to avoid MIX kctrl. To solve these issues, we need below. To avoid card re-binding issue: check registered card->controls To avoid duplicate DVC registration: check registered rsnd_kctrl_cfg To allow multiple MIX registration: check registered rsnd_kctrl_cfg This patch do it. Fixes: 9c698e8481a15237a ("ASoC: rsnd: tidyup registering method for rsnd_kctrl_new()") Reported-by: Jiada Wang <jiada_wang@mentor.com> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Tested-By: Jiada Wang <jiada_wang@mentor.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions