From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <vinod.koul@intel.com>, <dan.j.williams@intel.com>,
<lars@metafoo.de>, <tiwai@suse.de>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>, <joelf@ti.com>,
<nsekhar@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<dmaengine@vger.kernel.org>
Subject: [PATCH 0/4] ALSA/dmaengine: Fix 3 bytes physical sample support
Date: Wed, 2 Jul 2014 14:29:26 +0300 [thread overview]
Message-ID: <1404300570-14082-1-git-send-email-peter.ujfalusi@ti.com> (raw)
Hi,
I have noticed while switching the daVinci audio to dmaengine_pcm that the _3LE
and _3BE support is not working correctly via dmaengine_pcm:
In case of _3LE/_3BE formats the samples are stored in 3 consecutive bytes
without padding it to 4 bytes. This means that the DMA needs to be able to
support 3 bytes word length in order to read/write the samples from memory
correctly. Originally the code treated 24 bits physical length samples as
they were 32 bits which leads to corruption when playing or recording audio.
To fix the support for 3 bytes physical samples the dma driver also need to have
support for such data arrangement. eDMA does have support for it in HW and the
legacy davinci-pcm platform driver w/o dmaengine was able to support such
formats.
First step is to add DMA_SLAVE_BUSWIDTH_3_BYTES to dma_slave_buswidth for
engines and users to select 3 bytes as bus width.
Followed by:
In snd_dmaengine_pcm_open() we should check the slave_caps of the dma if it
supports DMA_SLAVE_BUSWIDTH_3_BYTES. Based on this information we initialize
the runtime->hw.formats: if DMA_SLAVE_BUSWIDTH_3_BYTES is not supported or
the slave_caps is not provided by the driver we mask out the 24 bits
physical width sample formats so they will be not available for user space
to pick. If the DMA_SLAVE_BUSWIDTH_3_BYTES is supported _3LE/_3BE formats
will not be masked so later on they can be valid if both CPU and codec dai
supports them.
Regards,
Peter
---
Peter Ujfalusi (4):
dma: Support for 3 bytes word size
dma: edma: Declare DMA_SLAVE_BUSWIDTH_3_BYTES as supported buswidth
ALSA: pcm_dmaengine: Use the available wrapper to get physical width
ALSA: pcm_dmaengine: Correct support for 3 physical bytes samples
drivers/dma/edma.c | 1 +
include/linux/dmaengine.h | 1 +
sound/core/pcm_dmaengine.c | 41 +++++++++++++++++++++++++++++++++++++++--
3 files changed, 41 insertions(+), 2 deletions(-)
--
2.0.0
next reply other threads:[~2014-07-02 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 11:29 Peter Ujfalusi [this message]
2014-07-02 11:29 ` [PATCH 1/4] dma: Support for 3 bytes word size Peter Ujfalusi
2014-07-02 11:29 ` [PATCH 2/4] dma: edma: Declare DMA_SLAVE_BUSWIDTH_3_BYTES as supported buswidth Peter Ujfalusi
2014-07-02 11:29 ` [PATCH 3/4] ALSA: pcm_dmaengine: Use the available wrapper to get physical width Peter Ujfalusi
2014-07-02 11:46 ` Lars-Peter Clausen
2014-07-02 11:29 ` [PATCH 4/4] ALSA: pcm_dmaengine: Correct support for 3 physical bytes samples Peter Ujfalusi
2014-07-02 12:44 ` Peter Ujfalusi
2014-07-02 12:48 ` Lars-Peter Clausen
2014-07-02 12:56 ` Peter 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=1404300570-14082-1-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=joelf@ti.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®