From: Johannes Berg <johannes@sipsolutions.net>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Benjamin Berg <benjamin@sipsolutions.net>,
Paul Collins <paul@briny.ondioline.org>
Subject: delayed dma trigger
Date: Mon, 23 Oct 2006 10:49:51 +0200 [thread overview]
Message-ID: <1161593391.6617.25.camel@ux156> (raw)
Hi,
For AOA, there are some DMA engine programming pitfalls I wasn't aware
of previously (actually, I was aware of the bug it triggered but not
quite why it happened). But now we have two questions about the trigger
callback.
(1)
When correctly using the i2s bus (aoa isn't at the moment), it is not
possible to immediately stop doing DMA, the DMA engine has to finish the
current period first, then go into a stop condition, and only after that
we can stop the engine completely. Hence, this can take quite a while
(up to the period length). Is it ok to set the stop condition and return
from the trigger function without having DMA stopped? It'll be
completely stopped asynchronously on the next interrupt, and we'd have
to make the hw_free callback wait for that, I guess.
(2)
Relating to that, if a start trigger comes in before the DMA engine is
stopped, it would be nice if we could just clear the stop condition and
let it continue to run. Can recording start at any arbitrary period in
the buffer relying only on the pointer callback?
[Actually, come to think of it, isn't this required for proper 'pause'
function during playback or recording? I guess aoa is wrong now then?]
johannes
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-10-23 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 8:49 Johannes Berg [this message]
2006-10-23 13:23 ` delayed dma trigger Takashi Iwai
2006-10-23 13:46 ` Johannes Berg
2006-10-23 14:11 ` Takashi Iwai
2006-10-23 14:31 ` Johannes Berg
2006-10-24 15:07 ` Takashi Iwai
2006-10-24 15:13 ` Johannes Berg
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=1161593391.6617.25.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=alsa-devel@alsa-project.org \
--cc=benjamin@sipsolutions.net \
--cc=paul@briny.ondioline.org \
--cc=tiwai@suse.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.