[PATCH v3 00/12] Add support for on demand pipeline setup/destroy
Mark Brown
broonie at kernel.org
Sat Oct 2 02:16:31 CEST 2021
On Mon, 27 Sep 2021 15:05:05 +0300, Peter Ujfalusi wrote:
> The previous, v2 of this series was sent by Daniel Baluta:
> https://lore.kernel.org/alsa-devel/20210917143659.401102-1-daniel.baluta@oss.nxp.com/
>
> We have agreed that it might be better that someone from Intel is going to take it
> from here as we already have the infrastructure up to test and verify the
> dynamic pipelines support.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/12] ASoC: topology: change the complete op in snd_soc_tplg_ops to return int
commit: 415717e1e367debe6344533f98eaeceb2dce52b3
[02/12] ASoC: SOF: control: Add access field in struct snd_sof_control
commit: 199a3754f2736808d7bfa4c962eaf89e1d17e462
[03/12] ASoC: SOF: topology: Add new token for dynamic pipeline
commit: 2c28ecad0d099ff914a0675f064db6e5b75e0756
[04/12] ASoC: SOF: sof-audio: add helpers for widgets, kcontrols and dai config set up
commit: 93d71245c655e639248c7c33db20074c71a89c1a
[05/12] AsoC: dapm: export a couple of functions
commit: d1a7af0979292b187bde0d556d26fe21bd64b832
[06/12] ASoC: SOF: Add new fields to snd_sof_route
commit: 0a2dea1f10106746e5ed033beaf403049cf8eb10
[07/12] ASoC: SOF: restore kcontrols for widget during set up
commit: 5f3aad73fcc2b301ed7d7ed60c1364e8c29741b1
[08/12] ASoC: SOF: Don't set up widgets during topology parsing
commit: 1b7d57d7178697ebdd9e6f21b4953ada168d2a61
[09/12] ASoC: SOF: Introduce widget use_count
commit: 8b0014169254513bda914ba5d49a09458a919488
[10/12] ASoC: SOF: Intel: hda: make sure DAI widget is set up before IPC
commit: 0acb48dd31e39b617bb12ca546b4fecd6ccb2972
[11/12] ASoC: SOF: Add support for dynamic pipelines
commit: 5fcdbb2d45df6afb654674379546996b0027aa3e
[12/12] ASoC: SOF: topology: Add kernel parameter for topology verification
commit: c0e7969cf9c4fd347b33a8056960e8448f6b51c0
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
More information about the Alsa-devel
mailing list