[PATCH 0/8] ASoC: SOF: Introduce generic (in)firmware tracing infrastructure

[Mark Brown]

On Mon, 16 May 2022 13:47:03 +0300, Peter Ujfalusi wrote:
> SOF is using dma-trace (or dtrace) as a firmware tracing method, which is only
> supported with IPC3 and it is not applicable for IPC4.
> 
> Currently the dtrace is 'open managed' regardless of IPC version (we do force
> disable it for IPC4, but the dtrace calls remain in place).
> 
> From the kernel point of view there are only few ops that needs to be exposed
> by the firmware tracing support and everything else is IPC private, should not
> be known by the core.
> 
> [...]

Applied to

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

Thanks!

[1/8] ASoC: SOF: Introduce IPC independent ops for firmware tracing support
      commit: 0cfbaee21fcbf131f02c475dbc15f8a18ee621bc
[2/8] ASoC: SOF: Rename dtrace_is_supported flag to fw_trace_is_supported
      commit: 25b17da691f3c1a7cc433f864fd4845998a5a37a
[3/8] ASoC: SOF: Clone the trace code to ipc3-dtrace as fw_tracing implementation
      commit: 671e0b90051ec19e83c12501905734fb808b944e
[4/8] ASoC: SOF: Switch to IPC generic firmware tracing
      commit: 1dedbe4f223cac603e871d91133b9aa3136fbc21
[5/8] ASoC: SOF: ipc3-dtrace: Move host ops wrappers from generic header to private
      commit: b69979a1ec2d9347a43bf0ebdad2c1eb23447ca6
[6/8] ASoC: SOF: Modify the host trace_init parameter list to include dmab
      commit: 4b49cbd1e7ebe4b000a7eedc4f910488da62c055
[7/8] ASoC: SOF: Introduce opaque storage of private data for firmware tracing
      commit: 08341b27bd2ee3c79265ef7925b3bc68a1790ab9
[8/8] ASoC: SOF: ipc3-dtrace: Move dtrace related variables local from sof_dev
      commit: 0683532999ab3890f44f832cd47feee9e2374c22

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