Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
	Jaroslav Kysela <perex@perex.cz>,  Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	 Peter Ujfalusi <peter.ujfalusi@gmail.com>,
	Jai Luthra <j-luthra@ti.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 alsa-devel@alsa-project.org, Devarsh Thakkar <devarsht@ti.com>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Jayesh Choudhary <j-choudhary@ti.com>
Subject: Re: [PATCH v2 0/2] Fixes for McASP and dmaengine_pcm
Date: Wed, 12 Jun 2024 21:21:01 +0100	[thread overview]
Message-ID: <171822366136.240528.8303514508385610793.b4-ty@kernel.org> (raw)
In-Reply-To: <20240610-asoc_next-v2-0-b52aaf5d67c4@ti.com>

On Mon, 10 Jun 2024 16:25:59 +0530, Jai Luthra wrote:
> This series fixes two patches:
> 
> 1. Fix the dmaengine API usage by calling dmaengine_synchronize() after
>    dmaengine_terminate_async() when xrun events occur in application
> 2. Use the McASP AFIFO property from DT to refine the period size,
>    instead of hardcoding minimum to 64 samples
> 
> [...]

Applied to

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

Thanks!

[1/2] ALSA: dmaengine: Synchronize dma channel in prepare()
      (no commit info)
[2/2] ASoC: ti: davinci-mcasp: Set min period size using FIFO config
      commit: c5dcf8ab10606e76c1d8a0ec77f27d84a392e874

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


      parent reply	other threads:[~2024-06-12 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 10:55 [PATCH v2 0/2] Fixes for McASP and dmaengine_pcm Jai Luthra
2024-06-10 10:56 ` [PATCH v2 1/2] ALSA: dmaengine: Synchronize dma channel in prepare() Jai Luthra
2024-06-11  0:45   ` Lars-Peter Clausen
2024-06-11 10:39     ` Mark Brown
2024-06-11 12:35       ` Jai Luthra
2024-06-10 10:56 ` [PATCH v2 2/2] ASoC: ti: davinci-mcasp: Set min period size using FIFO config Jai Luthra
2024-06-10 14:47   ` Péter Ujfalusi
2024-06-12 20:21 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=171822366136.240528.8303514508385610793.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=devarsht@ti.com \
    --cc=j-choudhary@ti.com \
    --cc=j-luthra@ti.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@gmail.com \
    --cc=tiwai@suse.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox