From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Zidan Wang <zidan.wang@freescale.com>,
Xiubo.Lee@gmail.com
Subject: Re: [PATCH v2] ASoC: imx-wm8958: add imx-wm8958 machine driver
Date: Tue, 1 Mar 2016 20:38:22 -0800 [thread overview]
Message-ID: <20160302043821.GA3361@Asurada-CZ80> (raw)
In-Reply-To: <20160302041101.GZ18327@sirena.org.uk>
On Wed, Mar 02, 2016 at 01:11:01PM +0900, Mark Brown wrote:
> > + [VOICE_DAI] = {
> > + .name = "Voice",
> > + .stream_name = "Voice",
> > + .cpu_dai_name = "snd-soc-dummy-dai",
> > + .codec_name = "wm8994-codec",
> > + .codec_dai_name = "wm8994-aif2",
> > + .platform_name = "snd-soc-dummy",
>
> Why are you mapping in dummy DAIs? If these devices aren't connected
> then they're not connected and you shouldn't represent them. If they
> are connected to something then describe those connections, possibly in
> followup patches if you have other devices you need to support upstream
> first.
>From his previous reply to me (he forgot to use reply-all), he
told me that he only tested the aif1 path in the release while
leaving aif2 and aif3 for future use.
In his schematics of the reference board, I found all three aifs
are "connected" but AIF2 and AIF3 are optional through jumpers.
So I think it might be better for him to make the driver flexible
by including all three aifs while creating dai-links depending on
the presence of corresponding cpu-dais.
Thanks
Nicolin
prev parent reply other threads:[~2016-03-02 4:38 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
2016-03-02 4:11 ` Mark Brown
2016-03-02 4:38 ` Nicolin Chen [this message]
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=20160302043821.GA3361@Asurada-CZ80 \
--to=nicoleotsuka@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=zidan.wang@freescale.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