On Tue, 7 Dec 2021 13:39:40 -0600, Pierre-Louis Bossart wrote:
This patchset revisits the Intel hardware support in SOF. The HDAudio DMA position information was not following hardware recommended programming sequences (similar changes are already part of the HDaudio legacy driver), and the stream assignment applied a work-around that was only needed on specific versions of hardware. These changes are not tagged as 'Fixes' and don't need to be applied to -stable versions.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: SOF: Intel: ICL: move ICL-specific ops to icl.c commit: c697ef868f596aba7a5e90be8eb10bf4d4a98990 [2/7] ASoC: SOF: Intel: hda-stream: limit PROCEN workaround commit: a792bfc1c2bc4b5e2311edc62e0efe5adec5d079 [3/7] ASoC: SOF: Intel: hda-ctrl: apply symmetry for DPIB commit: 12ce213821b77242b2217d08850ff972e1fb50bb [4/7] ASoC: SOF: hda-stream: only enable DPIB if needed commit: ae81d8fd57ff7d2b421c80f0f9426d9e775023b5 [5/7] ASoC: SOF: Intel: hda: add quirks for HDAudio DMA position information commit: 288fad2f71fa0b989c075d4984879c26d47cfb06 [6/7] ASoC: SOF: Intel: hda-dai: remove unused fields commit: 924631df4134d62b51a9442d97355eeba7ff613c [7/7] ASoC: SOF: Intel: add comment on JasperLake support commit: 290a7c5509b6f14c28e959392f3cbc4d5b2c9318
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