mbox series

[0/2] ASoC: SOF: ipc4: upport multiple configs for BE DAIs

Message ID 20230316141458.13940-1-peter.ujfalusi@linux.intel.com
Headers show
Series ASoC: SOF: ipc4: upport multiple configs for BE DAIs | expand

Message

Peter Ujfalusi March 16, 2023, 2:14 p.m. UTC 
Hi,

Backend DAIs may support multiple audio formats. Modify pipeline setup to select
a suitable configuration based on topology and frontend DAI runtime configuration.

The prime use case is BT offload support where we need the abality to select
different configuration on the BE side.

Regards,
Peter
--
Kai Vehmanen (2):
  ASoC: SOF: ipc4-pcm: support multiple configs for BE DAIs
  ASoC: SOF: ipc4-topology: use common helper function in copier prepare

 sound/soc/sof/ipc4-pcm.c      | 66 ++++++++++++++++++++++---
 sound/soc/sof/ipc4-topology.c | 92 ++++++++++++++++++++++++++---------
 2 files changed, 128 insertions(+), 30 deletions(-)

Comments

Mark Brown March 17, 2023, 4:40 p.m. UTC | #1 
On Thu, 16 Mar 2023 16:14:56 +0200, Peter Ujfalusi wrote:
> Backend DAIs may support multiple audio formats. Modify pipeline setup to select
> a suitable configuration based on topology and frontend DAI runtime configuration.
> 
> The prime use case is BT offload support where we need the abality to select
> different configuration on the BE side.
> 
> Regards,
> Peter
> --
> Kai Vehmanen (2):
>   ASoC: SOF: ipc4-pcm: support multiple configs for BE DAIs
>   ASoC: SOF: ipc4-topology: use common helper function in copier prepare
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: SOF: ipc4-pcm: support multiple configs for BE DAIs
      commit: 279e52d6b9f366f9930a0f90ee84e7d0a6a27b26
[2/2] ASoC: SOF: ipc4-topology: use common helper function in copier prepare
      commit: 37ec7ab49f951ef8c38102328b84d3dc7155dc68

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