From: Mike Looijmans <mike.looijmans@topic.nl>
To: Joel Fernandes <joelf@ti.com>
Cc: Mark Brown <broonie@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [alsa-devel] Query on Audio DMA using DMAEngine
Date: Thu, 04 Jul 2013 08:06:34 +0200 [thread overview]
Message-ID: <51D510EA.1030809@topic.nl> (raw)
In-Reply-To: <51D46598.6070005@ti.com>
On 07/03/2013 07:55 PM, Joel Fernandes wrote:
> Copying some more lists are we're also discussing the DMA controller in the
> SoCs. Thanks.
>
> On 07/03/2013 04: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.
>
> Hi Mark,
>
> When would it not be possible to cope with a large period size? Are there any
> guidelines on what to consider when fixing a period size?
>
> I see tegra and aux1x go upto .period_bytes_min = 1024
>
> About slots, following are no.of slots on some SoCs with EDMA:
>
> am1808 - 96 slots available + 32 taken up for channel but can be reused with
> some changes.
> am335x - 172 slots available + 64 taken up for channels
>
> On a slightly different note, about buffer_bytes_max, is there any drawback to
> setting it to a smaller value? Currently 128K is about what is used on davinci-pcm.
> My idea is to map to do the direct mapping to IRAM if the IRAM transfers are
> really what are preventing the under runs, but 128K will be too much for the
> buffer as we don't have that much IRAM infact it is just the boundary on am33xx
> (128K)
In any case, using the IRAM directly might have some use, because you
don't have to compete for the DDRRAM with other devices. But I never
understood what the ping-ping via IRAM was supposed to accomplish, I
don't see why McASP -> IRAM -> DDRRAM (or the other way around) would be
better than just McASP -> DDRRAM. Especially since the McASP has a
built-in 256 byte FIFO buffer on both channels. In all my measurements,
using the IRAM ping-pong only made things worse in terms of overruns and
underruns, not better.
Anyone who know why the ping-pong was implemented and what kind of usage
it was intended for?
Mike.
next prev parent reply other threads:[~2013-07-04 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <083BC63EECB6FD41B8E81CF7FD87CC0F2E4F1488@DLEE08.ent.ti.com>
[not found] ` <51D01F31.3010602@metafoo.de>
[not found] ` <51D11D64.3070805@topic.nl>
[not found] ` <51D24A01.2050709@ti.com>
[not found] ` <51D26A18.8040903@topic.nl>
[not found] ` <20130702121345.GL27646@sirena.org.uk>
[not found] ` <51D3EA42.3040205@metafoo.de>
[not found] ` <20130703094307.GE27646@sirena.org.uk>
[not found] ` <20130703094307.GE27646-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-07-03 17:55 ` [alsa-devel] Query on Audio DMA using DMAEngine 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 [this message]
2013-07-04 10:53 ` Mark Brown
[not found] ` <51D510EA.1030809-Oq418RWZeHk@public.gmane.org>
2013-07-04 10:59 ` [alsa-devel] " Sekhar Nori
[not found] ` <51D4245F.8070307@topic.nl>
[not found] ` <51D4245F.8070307-Oq418RWZeHk@public.gmane.org>
2013-07-03 19:56 ` Joel Fernandes
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=51D510EA.1030809@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=joelf@ti.com \
--cc=lars@metafoo.de \
--cc=linux-omap@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).