Message ID | 20201116133332.8530-1-cezary.rojewski@intel.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: Intel: catpt: Offload fixes and code optimization | expand |
On Mon, 16 Nov 2020 14:33:27 +0100, Cezary Rojewski wrote: > First two of the series address bugs connected mainly to offload streams: > - scenarios with very low buffer sizes: RESET_STREAM IPC timeouts > - fix lp clock selection when switching between PAUSE <-> RESUME states: > glitches on first offload when no additional stream is opened > simultaneously > > Follow ups are: code reduction and optimization oriented patches. > This has been foretold in: > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/5] ASoC: Intel: catpt: Skip position update for unprepared streams commit: aa9e3fa4992d83acb7311fc86d11d0d53e7ffb8e [2/5] ASoC: Intel: catpt: Correct clock selection for dai trigger commit: 1072460a1aabacf6ececda98acd3b5ecaad23fd2 [3/5] ASoC: Intel: catpt: Optimize applying user settings commit: 768a3a3b327da88c2fa6856806d32852a90e75d5 [4/5] ASoC: Intel: catpt: Streamline power routines across LPT and WPT commit: c440c72474e12fcf79bbe716d4796d16b7201031 [5/5] ASoC: Intel: catpt: Cleanup after power routines streamlining commit: 3d32489838bbf3119bb1ea59cdbed0077d7dbf3c 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