From: Mark Brown <broonie@kernel.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
paul.handrigan@cirrus.com, tim.howe@cirrus.com
Subject: Re: [PATCH v5] ASoC: cs53l30: Add support for Cirrus Logic CS53L30
Date: Tue, 31 May 2016 17:53:58 +0100 [thread overview]
Message-ID: <20160531165358.GH29837@sirena.org.uk> (raw)
In-Reply-To: <20160517234333.GB29471@Asurada-Nvidia>
[-- Attachment #1.1: Type: text/plain, Size: 780 bytes --]
On Tue, May 17, 2016 at 04:43:33PM -0700, Nicolin Chen wrote:
> In this case, would it be more appropriate to create one single DAI
> with channels_max = 4 over here?
Yes.
> Another question is for its TDM support. This chip outputs 4-channel
> data on two data output pins (SDOUT1 and SDOUT2) as normal mode; it
> outputs 4-channel data on one data output pin (SDOUT1) as TDM mode.
> However, the mode selection for a 4-channel recording should depend
> on the hardware design: whether the SDOUT2 is connected or not. So
> I am wondering if there is a common way or existing way to indicate
> this hardware design. Or just by simply defining a new DT property?
That's a really rare thing to have as an option, most things either do
TDM or parallel data signals but not both.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-05-31 16:54 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 [this message]
2016-05-31 17:10 ` Caleb Crome
2016-05-31 17:33 ` Handrigan, Paul
2016-05-31 17:35 ` Mark Brown
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=20160531165358.GH29837@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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 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).