On Thu, 16 Mar 2023 17:11:31 +0200, Peter Ujfalusi wrote:
The following series will add support for IPC4 process modules as effect widgets. We can cover wide range of modules as a generic process or effect module, the patches will lay down the fundation and the generic code to handle them.
At initialization time process modules can receive additional information on top of the base_cfg, which is defined as base_cfg_ext, an extension for the base configuration struct. Other parameters or blobs for these modules are sent as a separate message via LARGE_CONFIG message, which is handled by the existing bytes control support.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/6] ASoC: SOF: ipc4-topology: Move the kcontrol module_id update to helper commit: 04b522a4d2acf8447d69bf87b3ab67d5e6d631a2 [2/6] ASoC: SOF: ipc4-topology: add effect widget support commit: 7711a2bbc8447dd7185c6da9e405d89ce3ec2f0f [3/6] ASoC: SOF: ipc4-topology: add base module config extension structure commit: d0be868c5a6e0dafb53d0ee9f0b9d66e40d963f6 [4/6] ASoC: SOF: ipc4-topology: Add support for base config extension commit: f9efae954905a07a9d152e9b30546a6632227eef [5/6] ASoC: SOF: ipc4-topology: set copier output format for process module commit: 648fea12847695d60ddeebea86597114885ee76e [6/6] ASoC: SOF: ipc4-topology: update pipeline_params in process prepare commit: 811a742f2d4d1b0aee686bc2f4282b51534898a2
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