From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [Q] ASoC: What's the real meaning of SND_SOC_DAIFMT_NB_NF?
Date: Thu, 23 Feb 2012 15:19:34 +0000 [thread overview]
Message-ID: <20120223151934.GB4553@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACKLOr1sDSEFCiAsRO-vKrk7f+r=_Ex9irog1NKDmXn7LJFCDw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]
On Thu, Feb 23, 2012 at 01:40:40PM +0100, javier Martin wrote:
> As I wasn't sure about the meaning of 'normal' I've dug into the code
> of some platforms to see what they do. What I've found, however, is
> that it doesn't seem to be an agreement about it.
It's whatever is standard for the given format - the Wolfson datasheets
are a pretty good reference, they have clear diagrams.
> ALso, it seems that there is no possibility to specify different
> configurations for RX and TX parts.
This is correct, if the configurations are different you're really
looking at separate audio interfaces so should have multiple DAIs.
[-- 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-23 15:19 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 [this message]
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
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=20120223151934.GB4553@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=javier.martin@vista-silicon.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 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).