Message ID | 20220314200520.1233427-1-ranjani.sridharan@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | Introduce IPC abstraction for SOF topology parsing | expand |
On Mon, 14 Mar 2022 13:05:01 -0700, Ranjani Sridharan wrote: > This patchset makes the topology parsing layer in the SOF driver > IPC-agnostic in preparation for supporting the new IPC version > introduced in the SOF firmware. These patches purely contain abstraction > changes for the current IPC version (IPC3) supported and do not introduce > any functional changes. > > Ranjani Sridharan (18): > ASoC: SOF: Introduce struct snd_sof_dai_link > ASoC: SOF: IPC: Introduce IPC ops > ASoC: SOF: topology: Add helper function for processing tuple arrays > ASoC: SOF: Introduce IPC3 ops > ASoC: SOF: topology: Make scheduler widget parsing IPC agnostic > ASoC: SOF: topology: Make buffer widget parsing IPC agnostic > ASoC: SOF: topology: Make pga widget parsing IPC agnostic > ASoC: SOF: topology: Make mixer widget parsing IPC agnostic > ASoC: SOF: topology: Make mux/demux widget parsing IPC agnostic > ASoC: SOF: topology: Make src widget parsing IPC agnostic > ASoC: SOF: topology: Make asrc widget parsing IPC agnostic > ASoC: SOF: topology: Make siggen widget parsing IPC agnostic > ASoC: SOF: topology: Make effect widget parsing IPC agnostic > ASoC: SOF: topology: Make route setup IPC agnostic > ASoC: SOF: topology: Make DAI widget parsing IPC agnostic > ASoC: SOF: topology: Make control parsing IPC agnostic > ASoC: SOF: topology: Make widget binding IPC agnostic > ASoC: SOF: topology: remove snd_sof_complete_pipeline() > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/18] ASoC: SOF: Introduce struct snd_sof_dai_link commit: 0af0f4633adfa211807262af4d446b09698df6c8 [02/18] ASoC: SOF: IPC: Introduce IPC ops commit: 226abb759063ca53a32c1570d058db03b7850fdf [03/18] ASoC: SOF: topology: Add helper function for processing tuple arrays commit: d87524bf9aab511906e7e9bab90198510c28149f [04/18] ASoC: SOF: Introduce IPC3 ops commit: 7006d20e5e9d25c079a82e2bc0ea7e292fdea6e6 [05/18] ASoC: SOF: topology: Make scheduler widget parsing IPC agnostic commit: 2141b55d9174c7aa5b32da95a2caa807a018968a [06/18] ASoC: SOF: topology: Make buffer widget parsing IPC agnostic commit: 6bd0be1c29dc0c9b69636f11f80071d46e1e2285 [07/18] ASoC: SOF: topology: Make pga widget parsing IPC agnostic commit: 8a2e4a734f5ecbc48a3227c8ad68c12a71272c79 [08/18] ASoC: SOF: topology: Make mixer widget parsing IPC agnostic commit: 30f4168024e91e85aff9edcef561715ed271b34c [09/18] ASoC: SOF: topology: Make mux/demux widget parsing IPC agnostic commit: 683b54ef603825328859d867aabf9a6d973238a2 [10/18] ASoC: SOF: topology: Make src widget parsing IPC agnostic commit: 8d8b1293473022953ed316c3e0c723ff5a1505ac [11/18] ASoC: SOF: topology: Make asrc widget parsing IPC agnostic commit: cb7ed49acf585d45c1140660d076b389de7d468e [12/18] ASoC: SOF: topology: Make siggen widget parsing IPC agnostic commit: 111d66f62e9bf49ff33631c4e81efdcc4a54b88f [13/18] ASoC: SOF: topology: Make effect widget parsing IPC agnostic commit: f2cf24a1afa836be44dd2abdf7896b236df8d9a2 [14/18] ASoC: SOF: topology: Make route setup IPC agnostic commit: 85ec8560893cb9aae2728dd12f59537b6247d91f [15/18] ASoC: SOF: topology: Make DAI widget parsing IPC agnostic commit: 909dadf21aae8f7e604973218907ed39e10499e6 [16/18] ASoC: SOF: topology: Make control parsing IPC agnostic commit: b5cee8feb1d482a9d07b677f4f2f9565bacda53e [17/18] ASoC: SOF: topology: Make widget binding IPC agnostic commit: 8ef1439c51048b9359a8d1be2360dd4cd9848a77 [18/18] ASoC: SOF: topology: remove snd_sof_complete_pipeline() commit: 61ad28ff6cf349c3e25f6c4a56ce4d140c003d19 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