From: Zidan Wang <zidan.wang@freescale.com>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org, timur@tabi.org,
tiwai@suse.com
Subject: Re: [PATCH] ASoC: fsl-asoc-card: add wm8960 support
Date: Wed, 12 Aug 2015 15:39:00 +0800 [thread overview]
Message-ID: <20150812073859.GB21786@shlinux2> (raw)
In-Reply-To: <20150812064053.GA2807@Asurada-CZ80>
On Tue, Aug 11, 2015 at 11:40:54PM -0700, Nicolin Chen wrote:
> On Wed, Aug 12, 2015 at 12:45:10PM +0800, Zidan Wang wrote:
>
> > > > + /*
> > > > + * for imx6ul we should set SAI2_MCLK_DIR to enable
> > > > + * codec MCLK
> > > > + */
> > > > + if (of_device_is_compatible(np, "fsl,imx6ul-evk-wm8960"))
> > > > + regmap_update_bits(priv->gpr, 4, 1 << 20, 1 << 20);
>
> > > What's this SAI2_MCLK_DIR? Can you provide the description of it?
> > SAI2_MCLK_DIR: SD1_CLK data direction control when sai2.MCLK is selected (ALT2)
> > 0 SD1_CLK output driver is disabled when configured for ALT2
> > 1 SD1_CLK output driver is enabled when configured for ALT2
>
> > We are using SAI2 now, so we should enable SAI2_MCLK_DIR. If we want to
> > use SAI1 and SAI3, we should also enable SAI1_MCLK_DIR and SAI3_MCLK_DIR.
> > I don't consider SAI1 and SAI3 case, should i add it like below:
>
> Yes. Just think about a general interface/configuration that can
> satisfy all the MCLK cases you can imagine.
>
> Since it's a clock dealing with SAI, I think it would be better to
> put the configuration inside:
>
> 494 } else if (strstr(cpu_np->name, "sai")) {
> 495 priv->cpu_priv.sysclk_id[1] = FSL_SAI_CLK_MAST1;
> 496 priv->cpu_priv.sysclk_id[0] = FSL_SAI_CLK_MAST1;
> 497 }
>
> And I still don't understand the meaning of this MCLK at all.
> Does it indicate SAI's MCLK or an MCLK for external CODEC chips?
> Will it be possible that a user needs this MCLK bit to be unset?
For imx6ul-evk, MCLK for wm8960 CODEC chips and SAI's MCLK is the same pin.
So it should always be set for SAI.
>
> Can you share the document to me privately so I can give you a
> suggestion in detail?
>
> > > > - priv->dai_link[0].codec_dai_name = codec_dev->name;
> > > > + if (strstr(codec_dev->name, "wm8960"))
> > > > + priv->dai_link[0].codec_dai_name = "wm8960-hifi";
> > > > + else
> > > > + priv->dai_link[0].codec_dai_name = codec_dev->name;
>
> > > What happens to the codec_dev->name over here so that you need to
> > > specify the name?
> > In wm8960 codec driver, codec dai name is "wm8960-hifi".
> > Using codec_dev->name will cauce register card failed.
>
> When we meet a problem, the first response should be to find out
> the route cause instead of fixing it with a work around directly.
> If the codec_dev->name caused a card registration failure, you
> need to find out why. There must be something wrong with its codec
> driver or this sound card driver.
>
The root cause is that the codec dai name is not always be codec_dev->name. It will cause the sound card can't find such codec dai. You can refer to function snd_soc_find_dai().
For wm8962 the codec dai name and codec_dev->name are "wm8962". But some other codec like wm8960, it may have different codec dai name.
> Nicolin
next prev parent reply other threads:[~2015-08-12 8:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 3:22 [PATCH] ASoC: fsl-asoc-card: add wm8960 support Zidan Wang
2015-08-12 3:42 ` Nicolin Chen
2015-08-12 4:45 ` Zidan Wang
2015-08-12 6:40 ` Nicolin Chen
2015-08-12 7:39 ` Zidan Wang [this message]
2015-08-12 9:03 ` Nicolin Chen
2015-08-12 22:27 ` Nicolin Chen
2015-08-14 2:21 ` Zidan Wang
2015-08-14 3:58 ` Nicolin Chen
2015-08-14 7:38 ` Zidan Wang
2015-08-14 9:22 ` Nicolin Chen
2015-09-06 11:33 ` Shawn Guo
2015-09-17 8:03 ` Nicolin Chen
2015-09-18 13:19 ` Shawn Guo
2015-09-19 17:50 ` Nicolin Chen
2015-08-12 12:05 ` Fabio Estevam
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=20150812073859.GB21786@shlinux2 \
--to=zidan.wang@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=timur@tabi.org \
--cc=tiwai@suse.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).