From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: "Peter Ujfalusi" <peter.ujfalusi@ti.com>,
alsa-devel@alsa-project.org,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Eric Bénard" <eric@eukrea.com>
Subject: Re: [Q] ASoC: What's the real meaning of SND_SOC_DAIFMT_NB_NF?
Date: Fri, 24 Feb 2012 11:53:36 +0000 [thread overview]
Message-ID: <20120224115335.GC5450@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACKLOr14EHqGWcYCfLK0WXiVZsewDVyFPV2tpfYJK4tBZKMUXg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 852 bytes --]
On Fri, Feb 24, 2012 at 12:05:09PM +0100, javier Martin wrote:
> On 24 February 2012 09:34, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> > I don't think it is going to break. I would guess that the channels are
> > swapped on these machines at the moment. If you correct the CPU dai
> > driver the only thing that will happen is that the channels will jump in
> > their correct place.
> That would be true for stereo. However, mono should not be working right now.
Mono isn't particularly defined for I2S at the best of times; the
clocking is inherently stereo. You may just pick out the left channel
or you may duplicate things on left and right channels (at which point a
polarity change won't be noticed). I wouldn't worry too much about it,
it's better to have things the right way round and fix up configuration
for machines that need it.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-02-24 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 12:40 [Q] ASoC: What's the real meaning of SND_SOC_DAIFMT_NB_NF? javier Martin
2012-02-23 15:19 ` Mark Brown
2012-02-23 15:58 ` javier Martin
2012-02-23 16:14 ` Mark Brown
2012-02-24 7:53 ` javier Martin
2012-02-24 8:34 ` Peter Ujfalusi
2012-02-24 11:05 ` javier Martin
2012-02-24 11:53 ` Mark Brown [this message]
2012-02-24 14:09 ` Peter Ujfalusi
2012-02-24 11:20 ` Mark Brown
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=20120224115335.GC5450@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=eric@eukrea.com \
--cc=javier.martin@vista-silicon.com \
--cc=peter.ujfalusi@ti.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 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.