From: Nicolin Chen <b42378@freescale.com>
To: Mark Brown <broonie@kernel.org>
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 18:08:39 +0800 [thread overview]
Message-ID: <20130614100838.GC9206@MrMyself> (raw)
In-Reply-To: <20130614095917.GG1403@sirena.org.uk>
Hi,
On Fri, Jun 14, 2013 at 10:59:17AM +0100, Mark Brown wrote:
> The biases should be being managed using set_bias_level() which will get
> called automatically when audio is being started and stopped.
I understand your point because I also found other wm89xx drivers do this way.
But the truth is, originally this 8962 codec driver did put biases settings
into set_bias_level() as the others. But after commit d23031a4d they're put
into pm_resume().
So I can also see the point that it's reasonable to handle these settings in
pm_resume() since DAPM would call pm_runtime_get_sync(), so as snd_soc_open()
would though, pm_resume() would then finish the settings before the bias level
being set to STANDBY, according to dapm_pre_sequence_async() func.
As far as I can understand, I think these two approaches should be running
into a same consequence, while I'm not sure which one's better.
Sir, do you still think it's better to put them back into set_bias_level()?
Could you please help me understand the reason?
Thank you and looking forward to your reply.
Nicolin Chen
next prev parent reply other threads:[~2013-06-14 10:29 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 [this message]
2013-06-14 10:51 ` Mark Brown
2013-06-14 11:07 ` Nicolin Chen
2013-06-14 11:21 ` Mark Brown
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=20130614100838.GC9206@MrMyself \
--to=b42378@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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.