On Fri, 9 Sep 2022 14:43:25 +0300, Peter Ujfalusi wrote:
The traditional dtrace used by SOF IPC3 is not available with firmware built as IPC4. With the new IPC implementation we have a new log extraction infrastructure and 'mtrace' is one way to get the logs out from the firmware for debugging.
The protocol is relatively simple: The shared sram's debug window is split up to 'slots' Each DSP core will get a dedicated slot assigned for log output. The function of a slots can be checked in a descriptor table. The slot used for logging has the following layout:
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: SOF: ipc4: Only print LOG BUFFER update message info if requested commit: 621a3f772be5cfcd472880aa12ccb10d4c7afae3 [2/7] ASoC: SOF: ipc4: Add macro to get core ID from log buffer status message commit: e9bcfea156b4d8563109c17c033fa496f0ec4995 [3/7] ASoC: SOF: ipc4: Add define for the outbox window index commit: b59f1532e0b17f22965e327f86d04292f496ccaf [4/7] ASoC: SOF: ipc4: Configure the debug box offset commit: a5d0147ac9f8ea6c08d00b28f0468c9cb3fdfde8 [5/7] ASoC: SOF: ipc4: Add support for mtrace log extraction commit: f4ea22f7aa7536560097d765be56445933d07e0d [6/7] ASoC: SOF: Intel: icl: Set IPC4-specific DSP ops commit: 9ee71a31602fe72111b7a2d188ff84f7ead4cf92 [7/7] ASoC: SOF: Intel: Add mtrace type information for IPC4 commit: cc4a3a19b986aa13a488c8f319e413e85308f403
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