On Fri, 27 Jan 2023 14:00:13 +0200, Peter Ujfalusi wrote:
The following series will enable multi-stream support for playback and capture streams. Currently only a single PCM can be connected to a DAI, with the multi-stream support it is possible to connect multiple PCMs to a single DAI.
To achieve this we need to make sure that DAIs/AIF are only set up once since other stream could be connected to it later.
[...]
Applied to
broonie/sound.git for-next
Thanks!
[01/18] ASoC: SOF: ipc4-topology: No need to unbind routes within a pipeline commit: 9a62d87acee94919af1fe92f2412fff83dcbcda0 [02/18] ASoC: soc-pcm: Export widget_in_list() commit: 5edcf2a3aad41ee398ac011cda7bccca400b56f0 [03/18] ASoC: SOF: sof-audio: Set up/free DAI/AIF widgets only once commit: 73ea660947b52969214473434396a33d283c5ac8 [04/18] ASoC: SOF: sof-audio: Only process widgets in the connected widget list commit: 4639029b046bcab11bd566afa2979c68edeb338a [05/18] ASoC: SOF: pcm: do not free widgets during suspend trigger commit: 82b18242ae68214c44ccb13e993c2bc925f28428 [06/18] ASoC: SOF: topology: Set IPC-specific trigger order for DAI links commit: e380c9071032b89ea2e77b871792d908d0f15512 [07/18] ASoC: SOF: Introduce PCM setup/free PCM IPC ops commit: 7201a3d47e8a6a0b3a55125e70a9c650afabe7b0 [08/18] ASoC: SOF: ipc4-pcm: Define pcm_setup/free ops commit: ba223b3ad0b9f1753f0822c5c441a925cc82b63a [09/18] ASoC: SOF: ipc4: Add flag to skip triggering pipelines during FE DAI trigger commit: 37a26eec53b09b7054234b77200ce729601b0ccb [10/18] ASoC: SOF: sof-audio: Populate the PCM stream pipeline_info commit: 19137532dbe32ff2c8b5b1442c077bf3abff86f3 [11/18] ASoC: SOF: ipc4-pcm: Use the PCM stream's pipeline_info during trigger commit: 2d271af1af241e64726ada07c6bef6572f1be6a5 [12/18] ASoC: SOF: Introduce struct snd_sof_pipeline commit: 9c04363d222bc94d49d883458b2854334a848b5f [13/18] ASoC: SOF: ipc4-pcm: Rename 'data' variable to trigger_list commit: 6f9eb19a33d608ba36162a9ccbd34a77249fcc2e [14/18] ASoC: SOF: ipc4-pcm: Implement pipeline trigger reference counting commit: 32c4b69872e5fe5fd9517826be31dbf2c3dd917a [15/18] ASoC: SOF: ipc4-topology: Protect pipeline free with mutex commit: 6bc4d1b714aafc0ee3c7649c36aa19998b4c11f9 [16/18] ASoC: SOF: Avoid double decrementing use_count in sof_widget_setup on error commit: 955a6f131a50c3685c560ef7b75880d272337b33 [17/18] ASoC: SOF: Protect swidget->use_count with mutex for kcontrol access race commit: f94f3915274d22d5cd8b253e0533822b934f5f41 [18/18] ASoC: SOF: ipc4-pcm: Do not run the trigger pipelines if no spipe is stored commit: 251a2b11851531526260db1dbc5673a7d6177895
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