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>,
davinci-linux-open-source@linux.davincidsp.com,
linux-omap@vger.kernel.org
Subject: Re: Query on Audio DMA using DMAEngine
Date: Thu, 04 Jul 2013 07:56:25 +0200 [thread overview]
Message-ID: <51D50E89.5090503@topic.nl> (raw)
In-Reply-To: <20130703181226.GY27646@sirena.org.uk>
On 07/03/2013 08:12 PM, Mark Brown wrote:
> On Wed, Jul 03, 2013 at 12:55:36PM -0500, Joel Fernandes wrote:
>
>> 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?
>
> This is an application issue not a driver issue. An application that
> wants low latency may need high resolution information about what
> exactly the hardware is doing.
To get low-latency, the best thing from userspace is to mmap the audio
buffer, and monitor the position of the DMA transfers. If the driver
reports the DMA position accurately, you can get latencies of only a few
samples. I must admit that I know next to nothing about how ALSA works
in userspace, but that's how DirectSound works, for example. And from
what I've seen, this is also possible with ALSA.
Even without that - I tried with small periods of only 40 samples, this
invariably fails on the current driver, with or without the ping-ping.
Using the cyclic DMA I had no problem using such small periods.
Mike.
next prev parent reply other threads:[~2013-07-04 5:56 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
[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 [this message]
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=51D50E89.5090503@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 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.