mbox series

[0/2] ASoC: SOF: Intel: hda: Use cold/purge boot after firmware crash

Message ID 20220712120936.28072-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: Intel: hda: Use cold/purge boot after firmware crash | expand

Message

Peter Ujfalusi July 12, 2022, 12:09 p.m. UTC
Hi,

In case of a firmware crash we force the DSP to be powered down and rebooted.
To make sure that the next boot is going to be clean, force the boot process to
skip the IMR booting and re-download the firmware.

Regards,
Peter
---
Peter Ujfalusi (2):
  ASoC: SOF: Intel: hda: Introduce skip_imr_boot flag
  ASoC: SOF: Intel: hda: Skip IMR boot after a firmware crash or boot
    failure

 sound/soc/sof/intel/hda-dsp.c    | 12 ++++++++++++
 sound/soc/sof/intel/hda-loader.c | 10 ++++++----
 sound/soc/sof/intel/hda.h        |  1 +
 3 files changed, 19 insertions(+), 4 deletions(-)

Comments

Mark Brown July 12, 2022, 3:10 p.m. UTC | #1
On Tue, 12 Jul 2022 15:09:34 +0300, Peter Ujfalusi wrote:
> In case of a firmware crash we force the DSP to be powered down and rebooted.
> To make sure that the next boot is going to be clean, force the boot process to
> skip the IMR booting and re-download the firmware.
> 
> Regards,
> Peter
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: Intel: hda: Introduce skip_imr_boot flag
      commit: 57724db17a946476f11c1b1be9750bc0cf877adc

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