mbox series

[0/2] ASoC: SOF: ipc4: Fixup dailink format based on copier

Message ID 20230915093507.7242-1-peter.ujfalusi@linux.intel.com
Headers show
Series ASoC: SOF: ipc4: Fixup dailink format based on copier | expand

Message

Peter Ujfalusi Sept. 15, 2023, 9:35 a.m. UTC 
Hi,

If the copier supports a single format on the DAI side we should fixup the BE
dailink to use this single format.

Regards,
Peter
---
Bard Liao (2):
  ASoC: SOF: ipc4-topology: export sof_ipc4_copier_is_single_format
  ASoC: SOF: ipc4-pcm: fixup dailink based on copier format

 sound/soc/sof/ipc4-pcm.c      | 55 ++++++++++++++++++++++++++++++-----
 sound/soc/sof/ipc4-topology.c |  8 ++---
 sound/soc/sof/ipc4-topology.h |  3 ++
 3 files changed, 54 insertions(+), 12 deletions(-)

Comments

Mark Brown Sept. 16, 2023, 1:11 a.m. UTC | #1 
On Fri, 15 Sep 2023 12:35:05 +0300, Peter Ujfalusi wrote:
> If the copier supports a single format on the DAI side we should fixup the BE
> dailink to use this single format.
> 
> Regards,
> Peter
> 

Applied to

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

Thanks!

[1/2] ASoC: SOF: ipc4-topology: export sof_ipc4_copier_is_single_format
      commit: 94fc6da924072399e4f475c7d7124a7272197e6a
[2/2] ASoC: SOF: ipc4-pcm: fixup dailink based on copier format
      commit: 26dfc43461102957e33454e766d592df330ef7a0

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