From: Mike Looijmans <mike.looijmans@topic.nl>
To: Mark Brown <broonie@kernel.org>
Cc: Joel Fernandes <joelf@ti.com>,
alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: Query on Audio DMA using DMAEngine
Date: Wed, 03 Jul 2013 15:17:19 +0200 [thread overview]
Message-ID: <51D4245F.8070307@topic.nl> (raw)
In-Reply-To: <20130703094307.GE27646@sirena.org.uk>
On 07/03/2013 11:43 AM, Mark Brown wrote:
> On Wed, Jul 03, 2013 at 11:09:22AM +0200, Lars-Peter Clausen wrote:
>> On 07/02/2013 02:13 PM, Mark Brown wrote:
>
>>> This sort of cyclic thing tends to be best, ideally you don't need
>>> interrupts at all (other than a timer).
>
>> Yes, this is usually how it is done. But I'm wondering maybe the EDMA
>> controller only has a small total amount of slots available.
>
> Well, you don't need particularly many slots so long as you can cope
> with a large period size.
On the OMAP L138, there are 128 PARAM slots. 32 of those are tied to
hardware events (though you can use them if you aren't using the related
hardware, for example the UART drivers don't use DMA so you can freely
use those slots if you want), leaving (at least) 96 PARAM slots free.
Both audio events are on the same controller, so you can't use the 128
of the other one (the OMAP has 2 EDMA controllers). Only a few dozen of
those are being used by various drivers, the SD card driver being the
most hungry.
For the system to work, you can even get away with only using one slot,
and hence one period, but then you'll have to use a mmap and a timer to
fill it.
I experimented with various memory layouts. For large transfers, using 2
big periods was quite enough. I also tested with very small period
sizes. Using the original code, I was unable to reliably capture (to
/dev/null) at period sizes below 80 samples. With the cyclic DMA, I
could set a period size of only 40 samples and still be able to record
audio reliably, when using only 8 periods. The same for playback,
basically. So that's how I arrived at the MAX_PERIODS define of "8". It
will only claim channels when you use them, so setting it to say "100"
will not crash the system.
The period size is limited by the EDMA parameter set. It can only
transfer 64k-1 "words" per slot. You can (and should!) use the McASP
FIFO buffer to increase the word size, thus allowing for period sizes in
the megabyte range.
M.
next prev parent reply other threads:[~2013-07-03 13:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <083BC63EECB6FD41B8E81CF7FD87CC0F2E4F1488@DLEE08.ent.ti.com>
2013-06-30 12:06 ` Query on Audio DMA using DMAEngine Lars-Peter Clausen
2013-07-01 6:10 ` Mike Looijmans
2013-07-02 1:28 ` Joel Fernandes
2013-07-02 6:02 ` Mike Looijmans
2013-07-02 12:16 ` Mark Brown
2013-07-02 13:30 ` Mike Looijmans
2013-07-02 14:58 ` Mark Brown
2013-07-04 11:00 ` Clemens Ladisch
2013-07-02 3:33 ` Joel Fernandes
2013-07-02 5:50 ` Mike Looijmans
2013-07-02 12:13 ` Mark Brown
2013-07-02 13:40 ` Mike Looijmans
2013-07-03 9:09 ` Lars-Peter Clausen
2013-07-03 9:43 ` Mark Brown
2013-07-03 13:17 ` Mike Looijmans [this message]
[not found] ` <51D4245F.8070307-Oq418RWZeHk@public.gmane.org>
2013-07-03 19:56 ` Joel Fernandes
[not found] ` <20130703094307.GE27646-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-07-03 17:55 ` [alsa-devel] " Joel Fernandes
[not found] ` <51D46598.6070005-l0cyMroinI0@public.gmane.org>
2013-07-03 18:12 ` Mark Brown
2013-07-04 5:56 ` Mike Looijmans
2013-07-04 10:49 ` Mark Brown
2013-07-03 18:18 ` [alsa-devel] " Joel Fernandes
2013-07-04 6:06 ` Mike Looijmans
2013-07-04 10:53 ` Mark Brown
[not found] ` <51D510EA.1030809-Oq418RWZeHk@public.gmane.org>
2013-07-04 10:59 ` [alsa-devel] " Sekhar Nori
2013-08-14 4:30 ` Joel Fernandes
2013-08-14 4:53 ` Joel Fernandes
2013-08-14 14:10 ` Mike Looijmans
2013-08-14 12:06 ` Mark Brown
2013-07-02 1:04 ` Joel Fernandes
2013-07-03 9:07 ` Lars-Peter Clausen
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=51D4245F.8070307@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=joelf@ti.com \
--cc=lars@metafoo.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.