From: Mark Brown <broonie@sirena.org.uk>
To: christian pellegrin <chripell@gmail.com>
Cc: David Anders <dave123_aml@yahoo.com>,
alsa-devel@alsa-project.org, Ben Dooks <ben-linux@fluff.org>
Subject: Re: possible problem in s3c24xx-pcm.c in git-devel branch
Date: Thu, 13 Nov 2008 16:09:36 +0000 [thread overview]
Message-ID: <20081113160936.GH31592@sirena.org.uk> (raw)
In-Reply-To: <cabda6420811130740u325cf60bse8401af768fb7340@mail.gmail.com>
On Thu, Nov 13, 2008 at 04:40:03PM +0100, christian pellegrin wrote:
> AFAIK it's limited to 2 transfers, one loaded and one running. It
Yes, exactly - meaning that when DMA is idle there's only the loaded
buffer.
> could beneficial to have more of them (so the DMA doesn't stop if one
> interrupt is delayed for too much time). But I don't know if it's so
> critical. A period (4k) with cd quality sound takes 23 ms to be
> played. An embedded system not responding to irqs for all this time
> probably has worse issues.
AIUI it's a bootstrapping issue: the problem is what happens when the
first DMA buffer completes if there isn't a new buffer ready. Once
there's a loaded buffer ready things are happy.
I'm wondering if adding a call to s3c24xx_pcm_enqueue() in the start
trigger after enabling the DMA might help matters, but I've not thought
that through at all.
next prev parent reply other threads:[~2008-11-13 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 14:57 possible problem in s3c24xx-pcm.c in git-devel branch christian pellegrin
2008-11-13 15:17 ` Mark Brown
2008-11-13 15:40 ` christian pellegrin
2008-11-13 16:09 ` Mark Brown [this message]
2008-11-14 12:46 ` Mark Brown
2008-11-14 16:20 ` christian pellegrin
2008-11-17 11:00 ` Mark Brown
2008-11-13 15:44 ` David Anders
2008-11-13 16:02 ` christian pellegrin
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=20081113160936.GH31592@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=chripell@gmail.com \
--cc=dave123_aml@yahoo.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 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.