All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Caleb Crome <caleb@crome.org>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	paul.handrigan@cirrus.com, "Howe, Tim" <tim.howe@cirrus.com>
Subject: Re: [PATCH v5] ASoC: cs53l30: Add support for Cirrus Logic CS53L30
Date: Tue, 31 May 2016 18:35:05 +0100	[thread overview]
Message-ID: <20160531173505.GI29837@sirena.org.uk> (raw)
In-Reply-To: <CAG5mAdw-gh2_ZQ17h3HS=pMZaW-bGhoKgNDz_hbwzw2rBKs8ig@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1547 bytes --]

On Tue, May 31, 2016 at 10:10:11AM -0700, Caleb Crome wrote:
> On Tue, May 31, 2016 at 9:53 AM, Mark Brown <broonie@kernel.org> wrote:

> > That's a really rare thing to have as an option, most things either do
> > TDM or parallel data signals but not both.

> Interesting comment.  While I'm sure that's true for the moment,
> microphone arrays are changing this quickly.  I fall into the oddball
> category that the main chips I use are the TLV320AIC34 and CS53L30,
> and both of them can switch between TDM mode or dual I2S mode for 4
> channel support.

I'm not sure why mic arrays would drive that, it's not like they're
particularly new or innovative technology here and multi channel output
has been even more widely available for a long time?

> Since I need to get many channels on board, and SoCs (except for TI)
> rarely have enough parallel I2S ports for mic arrays, I opt for TDM
> mode often.

Modern systems all use TDM for the most part, the usage of parallel
data lines that I've seen has been for surround sound applications where
a 5.1 or 7.1 decoder will often be built by taking a bunch of high end
stereo CODECs and wiring them up in parallel, partly for performance and
physical design reasons and partly because such system designs have
often had their roots in very old systems.

This also matches the trend with more modern SoCs to use programmable
serial ports rather than dedicated I2S controllers so TDM is very easy
to configure, and of course it's fewer signals so it's easier from a
board design point of view too.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2016-05-31 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 22:47 [PATCH v5] ASoC: cs53l30: Add support for Cirrus Logic CS53L30 tim.howe
2016-03-28  9:51 ` Mark Brown
2016-05-17 23:43 ` Nicolin Chen
2016-05-31 16:53   ` Mark Brown
2016-05-31 17:10     ` Caleb Crome
2016-05-31 17:33       ` Handrigan, Paul
2016-05-31 17:35       ` Mark Brown [this message]
2016-05-31 22:32         ` Caleb Crome
2016-06-02 17:17           ` Mark Brown
2016-06-02 17:40             ` Caleb Crome
2016-06-02 18:40               ` Mark Brown
2016-06-05 16:48                 ` Caleb Crome
2016-06-06 18:11                   ` 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=20160531173505.GI29837@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=caleb@crome.org \
    --cc=lgirdwood@gmail.com \
    --cc=nicoleotsuka@gmail.com \
    --cc=paul.handrigan@cirrus.com \
    --cc=tim.howe@cirrus.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.