From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Haojian Zhuang <haojian.zhuang@marvell.com>,
alsa-devel@alsa-project.org,
Sven Neumann <s.neumann@raumfeld.com>, Liam Girdwood <lrg@ti.com>,
Daniel Mack <zonque@gmail.com>
Subject: Re: Swapped channels issue on pxa-ssp based platforms
Date: Tue, 8 Nov 2011 11:39:30 +0000 [thread overview]
Message-ID: <20111108113930.GI25591@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EB83D3B.2050906@ladisch.de>
On Mon, Nov 07, 2011 at 09:19:07PM +0100, Clemens Ladisch wrote:
> Daniel Mack wrote:
> > I guess this is some sort of a race condition in the stream startup,
> > and suspected sound/soc/pxa/pxa-ssp.c to lack some locking, so I added
> > a spinlock around all register read-modify-write cycles. But that doesn't
> > seem to be the reason.
> I'd guess this is a race in the programming of the L/R clock signals;
> try putting a lock/mutex about all the stream initialization code, and
> maybe adding some delay.
That's very unlikely to help, these issues are generally issues with the
controller not being able to figure out which clock edge to start on
properly and if there are problems here locking is unlikely to help -
the issue is the two hardware blocks synchronizing with each other,
usually with the clocks driven from an asynchronous domain.
next prev parent reply other threads:[~2011-11-08 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 17:40 Swapped channels issue on pxa-ssp based platforms Daniel Mack
2011-11-07 20:19 ` Clemens Ladisch
2011-11-08 11:39 ` Mark Brown [this message]
2011-11-08 11:46 ` Daniel Mack
2011-11-08 12:27 ` Mark Brown
2011-11-08 12:38 ` Daniel Mack
2011-11-08 2:54 ` Haojian Zhuang
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=20111108113930.GI25591@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=haojian.zhuang@marvell.com \
--cc=lrg@ti.com \
--cc=s.neumann@raumfeld.com \
--cc=zonque@gmail.com \
/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.