mbox series

[0/4] ASoC: SOF: ipc4-topology: Fixes for pipelines with SRC

Message ID 20230821113629.5017-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: ipc4-topology: Fixes for pipelines with SRC | expand

Message

Peter Ujfalusi Aug. 21, 2023, 11:36 a.m. UTC
Hi,

the SRC component in a pipeline provides flexibility on the sampling
rate which was not handled previously.

This series will improve the kernel side with the needed logic to be
able to deal with the SRC type of components in pipelines.

Regards,
Peter
---
Ranjani Sridharan (4):
  ASoC: SOF: ipc4-topology: Modify pipeline params based on SRC output
    format
  ASoC: SOF: ipc4-topology: Fix the output reference params for SRC
  ASoC: SOF: ipc4-topology: Fix pipeline params at the output of copier
  ASoC: SOF: ipc4-topology: Modify the reference output valid_bits for
    copier

 sound/soc/sof/ipc4-topology.c | 134 ++++++++++++++++++++++------------
 1 file changed, 89 insertions(+), 45 deletions(-)

Comments

Mark Brown Aug. 22, 2023, 4:33 p.m. UTC | #1
On Mon, 21 Aug 2023 14:36:25 +0300, Peter Ujfalusi wrote:
> the SRC component in a pipeline provides flexibility on the sampling
> rate which was not handled previously.
> 
> This series will improve the kernel side with the needed logic to be
> able to deal with the SRC type of components in pipelines.
> 
> Regards,
> Peter
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: SOF: ipc4-topology: Modify pipeline params based on SRC output format
      commit: ef24388225f87f2604522fe86fafacc271ec4a29
[2/4] ASoC: SOF: ipc4-topology: Fix the output reference params for SRC
      commit: 56ecc164040b3685f6cb36b4d513d73d0f88140b
[3/4] ASoC: SOF: ipc4-topology: Fix pipeline params at the output of copier
      commit: 769e8f6cd7182c95d4bd37491e13300ff067c7a7
[4/4] ASoC: SOF: ipc4-topology: Modify the reference output valid_bits for copier
      commit: 70b0924b22efe2135222a2c7141a83dfe0c78779

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