From: Mark Brown <broonie@kernel.org>
To: Nicolin Chen <b42378@freescale.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: WM8962: Enable start-up and normal bias after reset in runtime resume
Date: Fri, 14 Jun 2013 12:21:10 +0100 [thread overview]
Message-ID: <20130614112110.GL1403@sirena.org.uk> (raw)
In-Reply-To: <20130614110742.GD9206@MrMyself>
[-- Attachment #1.1: Type: text/plain, Size: 1009 bytes --]
On Fri, Jun 14, 2013 at 07:07:43PM +0800, Nicolin Chen wrote:
> On Fri, Jun 14, 2013 at 11:51:18AM +0100, Mark Brown wrote:
> > That said the general concept is that runtime PM would be powering on
> > the device for digital operation (eg, for the GPIOs) and then
> > set_bias_level() powering up the analogue portions of the device.
> Understood. But I just tested the set_bias_level() way to handle BIAS,
> it prompts "wm8962 0-001a: DC servo timed out" when I start to play a
> wav file. There should be still some parts of code not right.
> So I'm gonna just revise the comment to continue the resume() methods.
> It should be appropriate since pm_suspend() is handling bias-off in
> the current code.
If the DC servo is timing out that'll be a problem with the clocking...
the FLL is partially analogue so if you're using the FLL that makes
sense. Looking at the code we're also bringing the bias down in the
suspend path so it needs to be powered up in the resume path for
symmetry if nothing else.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-06-14 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 8:52 [PATCH] ASoC: WM8962: Enable start-up and normal bias after reset in runtime resume Nicolin Chen
2013-06-14 9:59 ` Mark Brown
2013-06-14 10:08 ` Nicolin Chen
2013-06-14 10:51 ` Mark Brown
2013-06-14 11:07 ` Nicolin Chen
2013-06-14 11:21 ` Mark Brown [this message]
2013-06-14 11:36 ` 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=20130614112110.GL1403@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.