On Fri, 10 Jun 2022 11:01:16 +0300, Peter Ujfalusi wrote: > This series handles the race which can result missing the first position update > after the trace is enabled. > In short: the firmware might send the position update (if we have enough > trace data generated) after the dma-trace is enabled by the TRACE_DMA_PARAMS_EXT > message. Depending on scheduling, load, preemption on Linux side we have seen > that occasionally this first position update got missed and we missed reading it > out. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/3] ASoC: SOF: ipc3-dtrace: Introduce SOF_DTRACE_INITIALIZING state commit: 135786c32ed057068bec56f67a54064cfc845bde [2/3] ASoC: SOF: ipc3-dtrace: Add helper function to update the sdev->host_offset commit: b66f9e703f0bee4e1aa7010299914b7b2009b4e0 [3/3] ASoC: SOF: ipc3-dtrace: Return from dtrace_read if there is no new data available commit: 1e90de2c9a40d7d0af5c7b0a6e2d362ffba94772 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