From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: TOMOHARU FUKAWA <tomoharu.fukawa.eb@renesas.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
shiiba <naoya.shiiba.nx@renesas.com>,
YOSHIFUMI HOSOYA <yoshifumi.hosoya.wj@renesas.com>,
shimoda <yoshihiro.shimoda.uh@renesas.com>,
Magnus <magnus.damm@gmail.com>,
komatsu <toshiaki.komatsu.ud@renesas.com>,
tanaka <hiroo.tanaka.sx@renesas.com>
Subject: Re: Question about codec which is supporting TDM / 5.1ch
Date: Wed, 21 Jan 2015 11:33:35 +0000 [thread overview]
Message-ID: <20150121113335.GE21293@sirena.org.uk> (raw)
In-Reply-To: <87oapsmvav.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1.1: Type: text/plain, Size: 818 bytes --]
On Wed, Jan 21, 2015 at 07:44:17AM +0000, Kuninori Morimoto wrote:
> Now, we want to create new board, and then, we want to use below codec if exist.
> Can you show it to us if it was exist ?
> (I researched it on upstream Linux source tree, but couldn't find....)
> - upstream Linux supports its driver
> - it supports TDM format
> - it supports 5.1ch sound
> - it supports DT bindings (if possible)
Some of the Wolfson/Cirrus mobile CODECs can do that with some fiddling
and mixing of output types but they're not really a good fit. Most of
the things doing 5.1 are like the WM8580 - they use separate data lines
rather than TDM, as far as I can tell a lot of 5.1 systems out there do
this by hooking up multiple stereo CODECs in parallel as slaves rather
than by using a single 5.1 CODEC.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-01-21 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SIXPR06MB0463DA8E64794D44FB73E300C1590@SIXPR06MB0463.apcprd06.prod.outlook.com>
[not found] ` <HKNPR06MB3221239EC2C1BA4FF216094B5590@HKNPR06MB322.apcprd06.prod.outlook.com>
[not found] ` <SIXPR06MB0463190557784E65CDBDD30FC1590@SIXPR06MB0463.apcprd06.prod.outlook.com>
[not found] ` <SIXPR06MB06548D6E23E7CD8B79F1BD44BC590@SIXPR06MB0654.apcprd06.prod.outlook.com>
[not found] ` <HKXPR06MB34170B809052DD484A1B62DA9460@HKXPR06MB341.apcprd06.prod.outlook.com>
[not found] ` <SIXPR06MB0463BD85668E6D68EEC9A5E3C1460@SIXPR06MB0463.apcprd06.prod.outlook.com>
[not found] ` <SIXPR06MB333851D089CC87404B679C1B5460@SIXPR06MB333.apcprd06.prod.outlook.com>
[not found] ` <54ACD3BF.9060107@renesas.com>
[not found] ` <HKXPR06MB0615ABF482506554FD9A7191D7460@HKXPR06MB0615.apcprd06.prod.outlook.com>
[not found] ` <54BE1BC0.6090408@renesas.com>
[not found] ` <HKXPR06MB0615D0AA32CC1219B1E5E95DD74B0@HKXPR06MB0615.apcprd06.prod.outlook.com>
[not found] ` <HKXPR06MB341C8969D2788FE21F887E2A94B0@HKXPR06MB341.apcprd06.prod.outlook.com>
[not found] ` <87ppa8mvqh.wl%kuninori.morimoto.gx@renesas.com>
2015-01-21 7:44 ` Question about codec which is supporting TDM / 5.1ch Kuninori Morimoto
2015-01-21 11:33 ` Mark Brown [this message]
2015-01-22 1:04 ` Kuninori Morimoto
2015-01-21 12:05 ` Lars-Peter Clausen
2015-01-22 1:05 ` Kuninori Morimoto
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=20150121113335.GE21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=hiroo.tanaka.sx@renesas.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=magnus.damm@gmail.com \
--cc=naoya.shiiba.nx@renesas.com \
--cc=tomoharu.fukawa.eb@renesas.com \
--cc=toshiaki.komatsu.ud@renesas.com \
--cc=yoshifumi.hosoya.wj@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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