From: Mark Brown <broonie@kernel.org>
Date: Mon, 16 Mar 2026 13:38:10 +0000 (+0000)
Subject: ASoC: soc-component: re-add pcm_new()/pcm_free()
X-Git-Tag: v7.1-rc1~166^2~5^2~86
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0861893cff96624523adc0968587fa64e9a9f76d;p=thirdparty%2Flinux.git

ASoC: soc-component: re-add pcm_new()/pcm_free()

Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> says:

Because old pcm_new()/pcm_free() didn't care about parameter component,
to avoid name collisions, we have added pcm_construct()/pcm_destruct() by
commit c64bfc9066007 ("ASoC: soc-core: add new pcm_construct/pcm_destruct")

Because all driver switch to new pcm_construct()/pcm_destruct(), old
pcm_new()/pcm_free() were remoted by commit e9067bb502787 ("ASoC:
soc-component: remove snd_pcm_ops from component driver")

But naming of pcm_construct()/pcm_destruct() are not goot. re-add
pcm_new()/pcm_free(), and switch to use it, again.

Because it has no functional significance, 1 patch is for 1 vender.
---

0861893cff96624523adc0968587fa64e9a9f76d