From: Rene Herman <rene.herman@keyaccess.nl>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
ALSA devel <alsa-devel@alsa-project.org>,
mulix@mulix.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] looping S/PDIF data
Date: Sat, 21 Jun 2008 14:14:38 +0200 [thread overview]
Message-ID: <485CF0AE.3020204@keyaccess.nl> (raw)
In-Reply-To: <20080621010910.018f880d@mjolnir.drzeus.cx>
On 21-06-08 01:09, Pierre Ossman wrote:
> trident: pause s/pdif output
>
> Stop the S/PDIF DMA engine and output when the device is told to pause.
> It will keep on looping the current buffer contents if this isn't done.
>
> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
Verified to fix the reported pause problem on a 4DWaveNX (and indeed to
not affect a 4DWaveDX). The Trident SPDIF doesn't seem capable of 44100
which for me means it's not all that useful but you no doubt know
yourself that/if it is for you...
Tested-by: Rene Herman <rene.herman@gmail.com>
Rene.
next prev parent reply other threads:[~2008-06-21 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 9:26 looping S/PDIF data Pierre Ossman
2008-06-02 8:00 ` Takashi Iwai
2008-06-17 19:55 ` Pierre Ossman
2008-06-18 7:24 ` Rene Herman
2008-06-19 10:05 ` [alsa-devel] " Takashi Iwai
2008-06-19 12:39 ` Jaroslav Kysela
2008-06-19 12:48 ` Takashi Iwai
2008-06-20 19:45 ` Pierre Ossman
2008-06-20 19:52 ` Rene Herman
2008-06-20 22:00 ` Pierre Ossman
2008-06-20 22:23 ` Rene Herman
2008-06-20 23:09 ` Pierre Ossman
2008-06-21 12:14 ` Rene Herman [this message]
2008-06-30 17:11 ` Pierre Ossman
2008-06-30 18:21 ` Rene Herman
2008-06-30 19:22 ` Pierre Ossman
2008-07-01 10:16 ` Takashi Iwai
2008-06-19 23:02 ` Pierre Ossman
2008-06-19 10:05 ` 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=485CF0AE.3020204@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=perex@perex.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox