[PATCH 0/6] ASoC: SOF: Rework the firmware ready message handling

[Mark Brown]

On Thu, 21 Apr 2022 11:07:29 +0300, Peter Ujfalusi wrote:
> The firmware ready (fw_ready) message is sent by the firmware to notify the host
> that it has been booted up and caries additional information about it's
> configuration.
> All of this is IPC specific, the message itself is IPC version specific and the
> information itself also.
> 
> Move the code to handle the fw_ready message under ipc3.c since the parsing and
> interpretation is IPC specific.
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: SOF: ipc3: Add local implementation for handling fw_ready message
      commit: b641fb7e019214d3fa2f44c3e562ba388e2a3933
[2/6] ASoC: SOF: Do not check for the fw_ready callback
      commit: cf64b67eebc222c9388adddc0038f9a59cb9511c
[3/6] ASoC: SOF: amd: Do not set fw_ready callback
      commit: 473dd4ea340c237e59d0c4d1973cf129a1bae504
[4/6] ASoC: SOF: imx: Do not set fw_ready callback
      commit: b5054161ebd168894b5a1d9d7eb97cd58dcbbb7f
[5/6] ASoC: SOF: Intel: Do not set fw_ready callback
      commit: 0fc88b5d42c646ecf4040f65c0f22cb9df42e69a
[6/6] ASoC: SOF: loader: Remove the old fw_ready related code
      commit: 19faf9ee06224c5db669539a10eae7c63f52f2e6

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