On Thu, 02 Feb 2023 15:29:45 +0200, Peter Ujfalusi wrote: > Changes since v2: > - Use div64_u64_rem() to make the code compile and work on non 64bit architectures > > Changes since v1: > - The delay calculation updated to take into account the counter wrapping on both > ends (host and link side). > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/9] ASoC: SOF: add ipc4_fw_reg header file commit: 2740dcce918f385aea0fb0a026cc0b91629479af [2/9] ASoC: SOF: add fw_info_box support commit: 4700bfb2bb3acae63ff4cbf82fbde35a325ebdf2 [3/9] ASoC: SOF: add time info structure for ipc4 path commit: 65a8ef494aff8bceac9a952ae8f6a1681231aee5 [4/9] ASoC: SOF: ipc4-pcm: allocate time info for pcm delay feature commit: af74dbd0dbcf49e8a3ae3e766683e13ecaf71e3b [5/9] ASoC: SOF: ipc4-pcm: add hw_params commit: 7cb19007baba0c7a76bd3f8f324a6b6548025968 [6/9] ASoC: SOF: add delay function support in sof framework commit: 27c2100b6bc8b0b064f89250eb4081431299115f [7/9] ASoC: SOF: add get_stream_position ops for pcm delay commit: 7f956297272bbc3535a02fa32579375a0d40283c [8/9] ASoC: SOF: Intel: mtl: add get_stream_position support commit: faceb3445aaf1704583744b48c622dbc96ef9ab2 [9/9] ASoC: SOF: ipc4-pcm: add delay function support commit: 3937a76c64931109dfafa999a0c78b4df2a6e0a1 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
