Message ID | 20220210105519.19795-1-peter.ujfalusi@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: SOF: IPC client infrastructure | expand |
On Thu, 10 Feb 2022 12:55:10 +0200, Peter Ujfalusi wrote: > The Linux SOF implementation is historically monolithic in a sense that all > features accessible in the firmware can be used via the snd_sof_dev struct in > one way or another. > > Support for features can not be added or removed runtime and with the current > way of things it is hard if not impossible to implement support for dynamic > feature support when based on the firmware manifest we can easily enable/access > independent modules with the SOF. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/9] ASoC: SOF: Drop unused DSP power states: D3_HOT and D3_COLD commit: 2439a35508277922ea116c99ff4d4a32c607464c [2/9] ASoC: SOF: Move the definition of enum sof_dsp_power_states to global header commit: 5fdc1242453e2ae88b2cdb607e4eda6b687f084c [3/9] ASoC: SOF: ipc: Read and pass the whole message to handlers for IPC events commit: ab3a2189a3744527f54ace1be19eb13e6c3d24df [4/9] ASoC: SOF: Split up utils.c into sof-utils and iomem-utils commit: ee8443050b2bf06d80fdd2c78cc25cae2abdedcd [5/9] ASoC: SOF: Introduce IPC SOF client support commit: 6955d9512d0ea814f1c2761bef7ad7b3cedf4d68 [6/9] ASoC: SOF: sof-client: Add support for clients not managed by pm framework commit: 1069967afe1e6b728061682ff99ec534a55a5613 [7/9] ASoC: SOF: Convert the generic IPC flood test into SOF client commit: 6e9548cdb30e5d6724236dd7b89a79a270751485 [8/9] ASoC: SOF: Convert the generic IPC message injector into SOF client commit: cac0b0887e5304bddfda91a4a7106f9328c31318 [9/9] ASoC: SOF: Convert the generic probe support to SOF client commit: 3dc0d709177828a22dfc9d0072e3ac937ef90d06 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