mbox series

[00/11] ASoC: SOF: ipc4: Add support for formats per pins

Message ID 20230313124856.8140-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: ipc4: Add support for formats per pins | expand

Message

Peter Ujfalusi March 13, 2023, 12:48 p.m. UTC
Hi,

The modules in IPC4 can have multiple 'pins' on their input and output and these
pins can receive or output audio in different formats.
Currently we assume that all pins are using the same format which is a limitation
that needs to be lifted in order to support more complex components.

This series will extend and rework the format handling to allow different formats
on pins.

Regards,
Peter
---

Ranjani Sridharan (11):
  ASoC: SOF: rename a couple of tokens
  ASoC: SOF: Use input/output pin consistently
  ASoC: SOF: ipc4-topology: Add a new field in struct
    sof_ipc4_available_audio_format
  ASoC: SOF: ipc4-topology: Do not parse the DMA_BUFFER_SIZE token
  ASoC: SOF: ipc4-topology: Parse the SOF_COMP_TOKENS only once
  ASoC: SOF: ipc4-topology: Always parse the output formats in topology
  ASoC: SOF: ipc4-topology: Modify the type of available input/output
    formats
  ASoC: SOF: ipc4-topology: Modify the signature of
    sof_ipc4_init_audio_fmt()
  ASoC: SOF: ipc4-topology: Remove the ref_audio_fmt field
  ASoC: SOF: ipc4-topology: Add new tokens for input/output pin format
    count
  ASoC: SOF: ipc4-topology: Search only pin 0 formats

 include/uapi/sound/sof/tokens.h |  20 +-
 sound/soc/sof/ipc4-pcm.c        |   2 +-
 sound/soc/sof/ipc4-topology.c   | 529 +++++++++++++++-----------------
 sound/soc/sof/ipc4-topology.h   |  36 ++-
 sound/soc/sof/sof-audio.h       |  35 +--
 sound/soc/sof/topology.c        | 124 ++++----
 6 files changed, 371 insertions(+), 375 deletions(-)

Comments

Mark Brown March 14, 2023, 3:12 p.m. UTC | #1
On Mon, 13 Mar 2023 14:48:45 +0200, Peter Ujfalusi wrote:
> The modules in IPC4 can have multiple 'pins' on their input and output and these
> pins can receive or output audio in different formats.
> Currently we assume that all pins are using the same format which is a limitation
> that needs to be lifted in order to support more complex components.
> 
> This series will extend and rework the format handling to allow different formats
> on pins.
> 
> [...]

Applied to

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

Thanks!

[01/11] ASoC: SOF: rename a couple of tokens
        commit: 3f738e4a126c9ee082d814edeb7416697f9e2b37
[02/11] ASoC: SOF: Use input/output pin consistently
        commit: bb79f2a608245cd92b3183d77aec6902e51de950
[03/11] ASoC: SOF: ipc4-topology: Add a new field in struct sof_ipc4_available_audio_format
        commit: e63a73f94fef0cf592aa7bb55f907007d747af4f
[04/11] ASoC: SOF: ipc4-topology: Do not parse the DMA_BUFFER_SIZE token
        commit: 594c1bb9ff7365b90cb4d325deb8c38ddda90557
[05/11] ASoC: SOF: ipc4-topology: Parse the SOF_COMP_TOKENS only once
        commit: 171d5ccedbb6277a8f9a3eae36e4f465ddc3187f
[06/11] ASoC: SOF: ipc4-topology: Always parse the output formats in topology
        commit: 8abc9ab956b5756693710e1e09557e0189f01bef
[07/11] ASoC: SOF: ipc4-topology: Modify the type of available input/output formats
        commit: 7ab6b1e8302cf7a9bc8808c43b3e751e4148a351
[08/11] ASoC: SOF: ipc4-topology: Modify the signature of sof_ipc4_init_audio_fmt()
        commit: 9c560549e32bc2951c67106c59587f9f7bf6b70e
[09/11] ASoC: SOF: ipc4-topology: Remove the ref_audio_fmt field
        commit: f534a94c3d765bcd5bdf10271a265883be2b4030
[10/11] ASoC: SOF: ipc4-topology: Add new tokens for input/output pin format count
        commit: 4fdef47a44d6ff735902dfe740918f23932225ca
[11/11] ASoC: SOF: ipc4-topology: Search only pin 0 formats
        commit: ad70f2f0e6e38675d7805482d2c625fca5756a2e

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