[v2,0/3] ASoC: Intel: avs: Add support for sending initial module config

Message

Amadeusz Sławiński Feb. 8, 2024, 10:23 a.m. UTC

In some cases it may be desirable to provide default initial
configuration for FW module using payload. To facilitate such solution
extend topology to contain initial config information, parse it and then
send data to FW if present.

Amadeusz Sławiński (3):
  ASoC: Intel: avs: UAPI: Add tokens for initial config feature
  ASoC: Intel: avs: Add topology parsing support for initial config
  ASoC: Intel: avs: Send initial config to module if present

 include/uapi/sound/intel/avs/tokens.h |   9 ++
 sound/soc/intel/avs/path.c            |  33 ++++++
 sound/soc/intel/avs/topology.c        | 164 +++++++++++++++++++++++++-
 sound/soc/intel/avs/topology.h        |  13 ++
 4 files changed, 217 insertions(+), 2 deletions(-)

Comments

Mark Brown Feb. 8, 2024, 8:22 p.m. UTC | #1

On Thu, 08 Feb 2024 11:23:57 +0100, Amadeusz Sławiński wrote:
> In some cases it may be desirable to provide default initial
> configuration for FW module using payload. To facilitate such solution
> extend topology to contain initial config information, parse it and then
> send data to FW if present.
> 
> Amadeusz Sławiński (3):
>   ASoC: Intel: avs: UAPI: Add tokens for initial config feature
>   ASoC: Intel: avs: Add topology parsing support for initial config
>   ASoC: Intel: avs: Send initial config to module if present
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: Intel: avs: UAPI: Add tokens for initial config feature
      commit: a5766cd479fd212e9831ceef8e9ab630c91445ab
[2/3] ASoC: Intel: avs: Add topology parsing support for initial config
      commit: 1b4217ebbb3e9d9b014db660618a4ddb61b3c321
[3/3] ASoC: Intel: avs: Send initial config to module if present
      commit: 8a49ef789b1be68242624d460df2ada8087308a7

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