[0/8] ASoC: qcom: q6asm: few fixes and enhancements.

Message

Srinivas Kandagatla June 11, 2020, 12:41 p.m. UTC

While trying out gapless playback, I found few issues with the existing code
This patchset has few fixes and some enhancement to the code to handle
multiple streams per asm session and also handle buffers that are not aligned
to period sizes.

I will send Gapless support patches once compressed gapless state machine is fixed.

Thanks,
srini

Srinivas Kandagatla (8):
  ASoC: q6asm: add command opcode to timeout error report
  ASoC: q6asm: handle EOS correctly
  ASoC: q6asm: rename misleading session id variable
  ASoC: q6asm: make commands specific to streams
  ASoC: q6asm: use flags directly from asm-dai
  ASoC: q6asm: add length to write command token
  ASoC: q6asm-dai: check available buffer size before sending
  ASoC: q6asm: allow to specify buffer offset in q6asm_write

 sound/soc/qcom/qdsp6/q6asm-dai.c | 100 ++++++++++++++--------
 sound/soc/qcom/qdsp6/q6asm.c     | 138 ++++++++++++++++++-------------
 sound/soc/qcom/qdsp6/q6asm.h     |  42 ++++++----
 3 files changed, 172 insertions(+), 108 deletions(-)

Comments

Mark Brown June 11, 2020, 3:28 p.m. UTC | #1

On Thu, 11 Jun 2020 13:41:51 +0100, Srinivas Kandagatla wrote:
> While trying out gapless playback, I found few issues with the existing code
> This patchset has few fixes and some enhancement to the code to handle
> multiple streams per asm session and also handle buffers that are not aligned
> to period sizes.
> 
> I will send Gapless support patches once compressed gapless state machine is fixed.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: q6asm: handle EOS correctly
      commit: 6476b60f32866be49d05e2e0163f337374c55b06

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