Message ID | 20240426152946.3078805-1-jbrunet@baylibre.com |
---|---|
Headers | show |
Series | ASoC: meson: tdm fixes | expand |
On Fri, 26 Apr 2024 17:29:37 +0200, Jerome Brunet wrote: > This patchset fixes 2 problems on TDM which both find a solution > by properly implementing the .trigger() callback for the TDM backend. > > ATM, enabling the TDM formatters is done by the .prepare() callback > because handling the formatter is slow due to necessary calls to CCF. > > The first problem affects the TDMIN. Because .prepare() is called on DPCM > backend first, the formatter are started before the FIFOs and this may > cause a random channel shifts if the TDMIN use multiple lanes with more > than 2 slots per lanes. Using trigger() allows to set the FE/BE order, > solving the problem. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/4] ASoC: meson: axg-fifo: use threaded irq to check periods commit: b11d26660dff8d7430892008616452dc8e5fb0f3 [2/4] ASoC: meson: axg-card: make links nonatomic commit: dcba52ace7d4c12e2c8c273eff55ea03a84c8baf [3/4] ASoC: meson: axg-tdm-interface: manage formatters in trigger commit: f949ed458ad15a00d41b37c745ebadaef171aaae [4/4] ASoC: meson: axg-tdm: add continuous clock support commit: a5a89037d080e0870d7517c61f8b2123d58ab33b 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