All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:07:43 +0800	[thread overview]
Message-ID: <20130614110742.GD9206@MrMyself> (raw)
In-Reply-To: <20130614105118.GI1403@sirena.org.uk>

On Fri, Jun 14, 2013 at 11:51:18AM +0100, Mark Brown wrote:
> Don't just quote commit IDs, use the subject lines as well so humans can
> read your e-mails.  The commit you're referring to moves some code out
> of set_bias_level() into runtime PM.

I'm sorry, I'll obey the rule from now on.

> So, if that's the case why are you changing this...  it may be that what
> you need to do is to write a better commit message so it's clear why
> you're making the change, your message just described what the code
> change does but not why it's being done in that way.

You're right. I'll revise it.

> 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 you still can't accept it, I will then trace the code next week.
It's Friday night here, and I'm starving now :(

Thank you,
Nicolin Chen

  reply	other threads:[~2013-06-14 11:13 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 [this message]
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=20130614110742.GD9206@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.