From: Zidan Wang <zidan.wang@freescale.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, broonie@kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v3] ASoC: wm8960: update pll and clock setting function
Date: Mon, 10 Aug 2015 16:08:06 +0800 [thread overview]
Message-ID: <20150810080805.GB15493@shlinux2> (raw)
In-Reply-To: <20150810083246.GH25225@opensource.wolfsonmicro.com>
On Mon, Aug 10, 2015 at 09:32:46AM +0100, Charles Keepax wrote:
> On Mon, Jul 13, 2015 at 04:41:00PM +0800, Zidan Wang wrote:
> > Add sysclk auto mode. When it's sysclk auto mode, if the MCLK is
> > available for clock configure, using MCLK to provide sysclk directly,
> > otherwise, search a available pll out frequcncy and set pll.
> >
> > Configure clock in hw_params may cause problems when using bypass style
> > paths without hw_params in machine driver getting called. So add configure
> > clock to set_bias_level.
> >
> > Signed-off-by: Zidan Wang <zidan.wang@freescale.com>
> > ---
> <snip>
> > @@ -711,6 +785,9 @@ static int wm8960_set_bias_level_out3(struct snd_soc_codec *codec,
> > case SND_SOC_BIAS_PREPARE:
> > switch (snd_soc_codec_get_bias_level(codec)) {
> > case SND_SOC_BIAS_STANDBY:
> > + ret = wm8960_configure_clocking(codec);
> > + if (ret)
> > + return ret;
>
> Is it right that we are calling wm8960_configure_clocking before
> clk_prepare_enable? As configure_clocking will enable the clocks
> shouldn't mclk be available before then?
The wm8960 codec don't need to enable MCLK to write register. So i think it's ok to enable MCLK at the last moment.
Best Regards,
Zidan Wang
next prev parent reply other threads:[~2015-08-10 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 8:41 [PATCH v3] ASoC: wm8960: update pll and clock setting function Zidan Wang
2015-08-04 1:28 ` Zidan Wang
2015-08-06 8:12 ` Charles Keepax
2015-08-10 8:32 ` Charles Keepax
2015-08-10 8:08 ` Zidan Wang [this message]
2015-08-10 13:47 ` Charles Keepax
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=20150810080805.GB15493@shlinux2 \
--to=zidan.wang@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=tiwai@suse.de \
/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