From: Jai Luthra <j-luthra@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Peter Ujfalusi <peter.ujfalusi@gmail.com>
Cc: <linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<alsa-devel@alsa-project.org>, Jai Luthra <j-luthra@ti.com>
Subject: [PATCH 0/2] Fixes for McASP and dmaengine_pcm
Date: Tue, 4 Jun 2024 15:31:49 +0530 [thread overview]
Message-ID: <20240604-asoc_next-v1-0-e895c88e744d@ti.com> (raw)
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
Signed-off-by: Jai Luthra <j-luthra@ti.com>
---
Jai Luthra (2):
ALSA: dmaengine: Synchronize dma channel in prepare()
ASoC: ti: davinci-mcasp: Set min period size using FIFO config
include/sound/dmaengine_pcm.h | 1 +
sound/core/pcm_dmaengine.c | 10 ++++++++++
sound/soc/soc-generic-dmaengine-pcm.c | 8 ++++++++
sound/soc/ti/davinci-mcasp.c | 9 +++++++--
4 files changed, 26 insertions(+), 2 deletions(-)
---
base-commit: d97496ca23a2d4ee80b7302849404859d9058bcd
change-id: 20240604-asoc_next-c063fcc190c6
Best regards,
--
Jai Luthra <j-luthra@ti.com>
next reply other threads:[~2024-06-04 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 10:01 Jai Luthra [this message]
2024-06-04 10:01 ` [PATCH 1/2] ALSA: dmaengine: Synchronize dma channel in prepare() Jai Luthra
2024-06-06 17:28 ` Péter Ujfalusi
2024-06-04 10:01 ` [PATCH 2/2] ASoC: ti: davinci-mcasp: Set min period size using FIFO config Jai Luthra
2024-06-06 17:13 ` Péter Ujfalusi
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=20240604-asoc_next-v1-0-e895c88e744d@ti.com \
--to=j-luthra@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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 \
/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