Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Zidan Wang <zidan.wang@nxp.com>,
	alsa-devel@alsa-project.org, Xiubo.Lee@gmail.com
Subject: Re: [PATCH v2] ASoC: imx-wm8958: add imx-wm8958 machine driver
Date: Tue, 1 Mar 2016 17:43:57 -0800	[thread overview]
Message-ID: <20160302014356.GA29297@Asurada-Nvidia> (raw)
In-Reply-To: <20160302013439.GL18327@sirena.org.uk>

On Wed, Mar 02, 2016 at 10:34:39AM +0900, Mark Brown wrote:
> On Tue, Mar 01, 2016 at 01:06:16AM -0800, Nicolin Chen wrote:
> 
> > I personally suggest you to use fsl-asoc-card. Since the Codec IC
> > provides three DAIs. And in the schematics, you do have three DAI
> > links. It sounds plausible to me that we might treat these three
> > DAI links as three different cards. Then use different compatible
> > names: "imx-audio-wm8958-aif1" and so on. And each one can also
> > has ASRC back-end support.
> 
> No, that's really not going to work very well - having the same CODEC
> with very tightly coupled clocking connected into three cards is just
> going to be a mess, especially for the WM8958 where AIF3 is mostly just
> a pinmux to the other two DAIs rather than something that could ever be
> fully independent.

I see. Thanks for the input.

  reply	other threads:[~2016-03-02  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  3:42 [PATCH v2] ASoC: imx-wm8958: add imx-wm8958 machine driver Zidan Wang
2016-02-26 20:52 ` Nicolin Chen
     [not found]   ` <AM3PR04MB1412F6FB7E5107BBA3AB9B559ABB0@AM3PR04MB1412.eurprd04.prod.outlook.com>
2016-03-01  9:06     ` Nicolin Chen
2016-03-02  1:34       ` Mark Brown
2016-03-02  1:43         ` Nicolin Chen [this message]
2016-03-02  4:11 ` Mark Brown
2016-03-02  4:38   ` Nicolin Chen

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=20160302014356.GA29297@Asurada-Nvidia \
    --to=nicoleotsuka@gmail.com \
    --cc=Xiubo.Lee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=zidan.wang@nxp.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