From: Takashi Iwai <tiwai@suse.de>
To: Luuk van Dijk <lvd@mndmttr.nl>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: full/half duplex support
Date: Thu, 18 Nov 2004 14:17:32 +0100 [thread overview]
Message-ID: <s5hpt2bqosz.wl@alsa2.suse.de> (raw)
In-Reply-To: <courier.4198D349.0001155D@outpost.mndmttr.nl>
At Mon, 15 Nov 2004 17:03:21 +0100,
Luuk van Dijk wrote:
>
> LS.
>
> I am currently writing a driver for the ADI 1836 on the (ongoing)
> blackfin/uclinux port (blackfin.uclinux.org) and I have some questions (that
> I'll post in separate mails, so that they may be separate threads)
>
> The particular hardware configuration I am programming for is full-duplex in
> principle, i.e. it should be no problem to send and receive pcm bitstreams
> simultaneously, except that it requires that both dma channels are started
> simultaneously. Currently, I configure an unused substream with a dummy dma
> buffer, but the alsa mid layer seems to handle this badly: it appears to
> re-triggers the last-started substream when it finds out that the dma is at
> an other address than it expects.
Sorry, the situation is not clear for me.
Do you mean substream as the ALSA term?
So, you have two or more substreams assigned to a single PCM device,
and the DMAs are free-running when the substreams are unused?
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-18 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 16:03 full/half duplex support Luuk van Dijk
2004-11-18 13:17 ` Takashi Iwai [this message]
2004-11-18 18:06 ` Luuk van Dijk
2004-11-19 12:13 ` Takashi Iwai
2004-11-19 20:29 ` Luuk van Dijk
2004-11-22 11:35 ` Takashi Iwai
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=s5hpt2bqosz.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=lvd@mndmttr.nl \
/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.