From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Eric Bénard" <eric@eukrea.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>, alsa-devel@alsa-project.org
Subject: Re: imx-ssi.c & SND_SOC_DAIFMT_I2S
Date: Wed, 26 May 2010 21:54:39 -0400 [thread overview]
Message-ID: <20100527015439.GA21618@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4BFDC7C7.7000507@eukrea.com>
On Thu, May 27, 2010 at 03:15:51AM +0200, Eric Bénard wrote:
> The problem on the first capture is that the SSI send the data for
> both channels on one half of the framesync's period => codec outputs
> sound on only one channel.
> By setting the mode to I2S_SLAVE, the SSI send the data the way the
> codec expect it : one channel when framesync is high and one channel
> when framesync is low.
Right, this is the thing I was saying about being unable to tolerate
extra BCLKs when in I2S mode. In general with these generic serial
ports you're much better off using one of the DSP modes, it's what they
naturally implement.
> >If I remember correctly the I2S slave mode isn't exactly I2S compliant
> >either and is actually just setting up similar settings to override
> >other registers. I could be wrong, or this could have changed in later
> >i.MXs.
> this is what is written in the comment, but in the iMX manual (at
> least 25 & 27), there is an I2S_SLAVE mode which seems to set more
> things than what is actually done in the driver as when I enable
> this, I get a perfect sound of both channels (and recording also
> works fine).
That register is present in later i.MX CPUs too, the issue is if it
actually does what is expected robustly.
next prev parent reply other threads:[~2010-05-27 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 9:34 imx-ssi.c & SND_SOC_DAIFMT_I2S Eric Bénard
2010-05-26 10:37 ` Sascha Hauer
2010-05-26 12:41 ` Eric Bénard
2010-05-27 0:56 ` Mark Brown
2010-05-27 1:15 ` Eric Bénard
2010-05-27 1:54 ` Mark Brown [this message]
2010-06-23 10:15 ` imx-ssi.c & SND_SOC_DAIFMT_I2S anilkumar
2010-06-23 10:28 ` Eric Bénard
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=20100527015439.GA21618@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=eric@eukrea.com \
--cc=s.hauer@pengutronix.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;
as well as URLs for NNTP newsgroup(s).