From: Daniel Mack <zonque@gmail.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [alsa-devel] channel swapping issue on OMAP3/TWL4030 is back
Date: Fri, 22 Mar 2013 10:07:34 +0100 [thread overview]
Message-ID: <514C1F56.7080403@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1303220958040.7975@pmeerw.net>
On 22.03.2013 10:03, Peter Meerwald wrote:
>
>>> I'm running Linux 3.7 on a beagle-xm and observe very reproducible stereo
>>> channel swapping issue on playback of a stereo stream (one channel has a
>>> sine, the other is zero); the channel swap occurs on starting the playback
>
>> Always? Or in like 50% of the runs? And is the record stream (IOW: the
>> clocks) already running when you switch on playback?
>
> in 10 runs, the swap can maybe observed 3 times; so: not always
>
> I can easily turn on/off the clock for the McBSP3/TLV320AIC3104 setup;
> with McBSP3 being master I ONLY have the issue when the clock is already
> running; when I start the stream first, then turn on the clock, there is
> NO SWAP
Yes, that sounds familiar. I guess the problem is that the serial line
driver does not respect a specific slope (like lo->hi) but will sync up
to *any* slope once it gets its enable bit set. Which will give you
arbitrary channel swaps.
Daniel
next prev parent reply other threads:[~2013-03-22 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 8:48 channel swapping issue on OMAP3/TWL4030 is back Peter Meerwald
2013-03-22 8:55 ` [alsa-devel] " Daniel Mack
2013-03-22 9:03 ` Peter Meerwald
2013-03-22 9:07 ` Daniel Mack [this message]
2013-03-22 9:56 ` Peter Meerwald
2013-03-22 10:11 ` Daniel Mack
2013-03-22 12:49 ` Peter Meerwald
2013-03-22 13:04 ` Peter Ujfalusi
2013-03-22 16:35 ` Russell King - ARM Linux
2013-03-25 12:39 ` Peter Ujfalusi
2013-03-25 17:15 ` Russell King - ARM Linux
2013-03-26 9:52 ` Peter Ujfalusi
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=514C1F56.7080403@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=pmeerw@pmeerw.net \
/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;
as well as URLs for NNTP newsgroup(s).