[PATCH 0/6] ASoC: SOF: ipc4/Intel: Improve and enable IPC error dump
Mark Brown
broonie at kernel.org
Tue Sep 27 12:34:25 CEST 2022
On Fri, 23 Sep 2022 16:36:10 +0300, Peter Ujfalusi wrote:
> On Intel platforms the registers for DSP communications are used differently,
> the IPC dump information is not correct since important registers are not
> printed and existing ones are used a bit differently for IPC4.
>
> As a last step, enable the IPC timeout 'handling' and allow the printout of
> the now usefull IPC dump.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/6] ASoC: SOF: Intel: cnl: Add separate ops for ipc_dump for IPC4
commit: a996a333ad74d1f26c3831f1edd94a5d16798a0c
[2/6] ASoC: SOF: Intel: hda: Add separate ops for ipc_dump for IPC4
commit: 32b97c07c2a3b7cccc0c7e9a5b23970bd9a52c5d
[3/6] ASoC: SOF: Intel: skl: Use the ipc4 version of the ipc_dump
commit: 6759f35b234aa94e26e122afcd402ba2a39bd9d3
[4/6] ASoC: SOF: Intel: mtl: Print relevant register in ipc_dump
commit: d01784ee680c558938baf6c4f184bee2bc612798
[5/6] ASoC: SOF: Intel: hda: Only dump firmware registers for IPC3
commit: 01fb69d09afb896579e00c3dbc3c1aa74613dd86
[6/6] ASoC: SOF: ipc4: Call snd_sof_handle_fw_exception() in case of timeout
commit: 4245fdba89b82befee0d963a85f7494c70432ee9
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
More information about the Alsa-devel
mailing list