From: Daniel Mack <daniel@caiaq.de>
To: Julian Scheel <julian@jusst.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Alex <lee188@singnet.com.sg>
Subject: Re: USB asynchronous mode feedback format
Date: Thu, 14 Oct 2010 13:56:20 +0200 [thread overview]
Message-ID: <20101014115620.GL10432@buzzloop.caiaq.de> (raw)
In-Reply-To: <201010141344.23599.julian@jusst.de>
On Thu, Oct 14, 2010 at 01:44:23PM +0200, Julian Scheel wrote:
> Am Donnerstag, 14. Oktober 2010, 13:15:45 schrieb Alex:
> > Channel inversion is a known issue and u need to sync the channel to the
> > LRCK, and resync when the USB stream is stopped and restarted and when
> > doing sample rate changes (48 to 96 etc).
>
> So far I only support one fixed sample rate (48 kHz) in the device. Regarding
> the sync I am wondering how to determine the alignment of the data coming from
> USB. Is there some way to be sure that the data frames do start with the left
> channel when reading them from USB?
Yes, a USB packet always starts at a sample frame boundary. In other
words, after the SOF, the USB stream will start with the first byte of
the first channel. One USB packet must also transport multiple full
audio frames (ie, samples for all channels), and not only fractions
thereof.
> The output to the I2S is done in bigger chunks through the DMA engine of the
> AT91SAM7 - it might be possible that I loose one packet in some case at this
> place... This would actually cause a inversion on the channels...
If you lose one entire packet and catch up with the next one, there
shouldn't be any channel inversion, just a data dropout. However I would
add an extra check to assure your internal counters are in sync whenever
a SOF is received.
Daniel
next prev parent reply other threads:[~2010-10-14 11:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 8:47 USB asynchronous mode feedback format lee188
2010-10-14 10:27 ` Julian Scheel
2010-10-14 10:48 ` Daniel Mack
2010-10-14 11:01 ` Julian Scheel
2010-10-14 11:16 ` Daniel Mack
2010-10-14 11:32 ` Julian Scheel
2010-10-14 12:06 ` Daniel Mack
2010-10-14 12:30 ` Julian Scheel
2010-10-14 12:33 ` Daniel Mack
2010-10-14 12:56 ` Julian Scheel
2010-10-14 15:10 ` Julian Scheel
2010-10-14 15:33 ` Alex Lee
2010-10-14 15:39 ` Daniel Mack
2010-10-14 15:54 ` Julian Scheel
2010-10-14 16:11 ` Daniel Mack
2010-10-14 20:14 ` Julian Scheel
2010-10-15 8:59 ` Julian Scheel
2010-10-15 9:03 ` Daniel Mack
2010-10-18 16:53 ` Julian Scheel
[not found] ` <3879AFD1-61E6-47FB-8ECB-8A7D7B233B3B@singnet.com.sg>
2010-10-14 11:44 ` Julian Scheel
2010-10-14 11:56 ` Daniel Mack [this message]
2010-10-14 11:58 ` Julian Scheel
2010-10-14 15:28 ` Alex Lee
2010-10-14 15:43 ` Julian Scheel
2010-10-15 12:08 ` Julian Scheel
2010-10-15 12:52 ` Alex Lee
2010-10-15 13:04 ` Julian Scheel
2010-10-15 13:31 ` Alex Lee
2010-10-15 14:24 ` Julian Scheel
2010-10-15 14:34 ` Clemens Ladisch
2010-10-16 10:23 ` Julian Scheel
2010-10-15 14:41 ` Alex Lee
2010-10-15 17:16 ` Julian Scheel
2010-10-15 17:19 ` Julian Scheel
2010-10-16 1:52 ` Alex Lee
2010-10-16 10:25 ` Julian Scheel
2010-10-16 13:58 ` Alex Lee
2010-10-16 16:30 ` Julian Scheel
2010-10-16 18:52 ` Julian Scheel
2010-10-17 10:53 ` Julian Scheel
2010-10-17 11:16 ` Alex Lee
-- strict thread matches above, loose matches on Subject: below --
2010-10-13 15:50 Julian Scheel
2010-10-14 1:28 ` Alex
2010-10-14 5:57 ` Julian Scheel
2010-10-14 6:25 ` Alex
2010-10-14 8:46 ` lee188
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=20101014115620.GL10432@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=julian@jusst.de \
--cc=lee188@singnet.com.sg \
/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.