From: Daniel Mack <daniel@caiaq.de>
To: Julian Scheel <julian@jusst.de>
Cc: alsa-devel@alsa-project.org, lee188@singnet.com.sg
Subject: Re: USB asynchronous mode feedback format
Date: Thu, 14 Oct 2010 13:16:12 +0200 [thread overview]
Message-ID: <20101014111612.GJ10432@buzzloop.caiaq.de> (raw)
In-Reply-To: <201010141301.52856.julian@jusst.de>
On Thu, Oct 14, 2010 at 01:01:52PM +0200, Julian Scheel wrote:
> Am Donnerstag, 14. Oktober 2010, 12:48:55 schrieb Daniel Mack:
> > On Thu, Oct 14, 2010 at 12:27:38PM +0200, Julian Scheel wrote:
> > > thanks a lot! You made my day (c:
> > > Using EP5 for feedback makes it working. So I now get the data out even
> > > in async mode. Currently I have a problem left that channel assignment
> > > jumps here and then. Probably a buffering issue...
> > > Also neither a SRC4192 (sample rate converter) nor a PCM1794 (dac) seem
> > > to be able to understand what I am sending right now... Not sure why.
> > > Looking at the measurements it really looks like a proper I2S signal.
> >
> > Can you send oscilloscope screenshots? Which data format are you using?
>
> Sure, attached you see a capture while running speaker-test to generate a 1khz
> sine wave on one channel. (Blue: BCLK 1,536MHz, Yellow: LRCLK: 48kHz, Green:
> I2S data)
> If you want to see more/other captures just let me know what you need.
The dump doesn't show whether the LRCLK is symmetrical, iow, whether the
low phase of LRCLK has the same number of BCLK cycles as the high phase.
But if that's the case, the signals do indeed look alright. Maybe you
need the configure the codec to this format?
Daniel
next prev parent reply other threads:[~2010-10-14 11:16 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 [this message]
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
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=20101014111612.GJ10432@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.