mbox series

[0/3] ASoC: SOF: query FW config to reload library

Message ID 20231215083102.3064200-1-yung-chuan.liao@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: query FW config to reload library | expand

Message

Liao, Bard Dec. 15, 2023, 8:30 a.m. UTC
We should query FW config if context save is supported, and no need
to reload FW if hda->booted_from_imr and ipc4_data->fw_context_save
are true.

Rander Wang (3):
  ASoC: SOF: IPC4: synchronize fw_config_params with fw definitions
  ASoC: SOF: IPC4: query fw_context_save feature from fw
  ASoC: SOF: Intel: check fw_context_save for library reload

 include/sound/sof/ipc4/header.h  | 6 ++++++
 sound/soc/sof/intel/hda-loader.c | 5 +++--
 sound/soc/sof/intel/lnl.c        | 2 ++
 sound/soc/sof/intel/mtl.c        | 2 ++
 sound/soc/sof/intel/tgl.c        | 2 ++
 sound/soc/sof/ipc4-loader.c      | 3 +++
 sound/soc/sof/ipc4-priv.h        | 1 +
 7 files changed, 19 insertions(+), 2 deletions(-)

Comments

Mark Brown Dec. 15, 2023, 6:56 p.m. UTC | #1
On Fri, 15 Dec 2023 16:30:59 +0800, Bard Liao wrote:
> We should query FW config if context save is supported, and no need
> to reload FW if hda->booted_from_imr and ipc4_data->fw_context_save
> are true.
> 
> Rander Wang (3):
>   ASoC: SOF: IPC4: synchronize fw_config_params with fw definitions
>   ASoC: SOF: IPC4: query fw_context_save feature from fw
>   ASoC: SOF: Intel: check fw_context_save for library reload
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: SOF: IPC4: synchronize fw_config_params with fw definitions
      commit: 57cd29a82574b0e9d99ed5789801c96f765e8fcb
[2/3] ASoC: SOF: IPC4: query fw_context_save feature from fw
      commit: 855a4772be9dc777cbcd580c8a07d9c54908219b
[3/3] ASoC: SOF: Intel: check fw_context_save for library reload
      commit: 3a0e7bb86f8728d94d55c56fb73e86be7976c163

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