All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Shaoming Feng <shaomingf@nvidia.com>
Cc: Daniel Solomon <daniels@nvidia.com>,
	Stephen Warren <swarren@nvidia.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ASoC: supply and micbiases shoud bring "up to" STANDBY
Date: Thu, 25 Oct 2012 17:49:18 +0100	[thread overview]
Message-ID: <20121025164917.GR18814@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F37A052B72B@HQMAIL04.nvidia.com>


[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]

On Wed, Oct 24, 2012 at 02:19:35PM -0700, Shaoming Feng wrote:

> /* Supplies and micbiases only bring the
>  * context up to STANDBY as unless something
>  * else is active and passing audio they
>   * generally don't require full power.  Signal
>   * generators are virtual pins and have no
>   * power impact themselves.
>   */

> According to the comment, the target bias level shouldn't be higher than STANDBY.

>                         case snd_soc_dapm_clock_supply:
>                         case snd_soc_dapm_micbias:
> -                               if (d->target_bias_level < SND_SOC_BIAS_STANDBY)
> +                              if (d->target_bias_level > SND_SOC_BIAS_STANDBY)
>                                         d->target_bias_level = SND_SOC_BIAS_STANDBY;

This will do the wrong thing - it'll mean that if we've already found
that we need a bias level over _STANDBY we'll pull back to only
selecting _STANDBY.  The intention here is that we should raise to
_STANDBY but this shouldn't distrupt operation of other widgets.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



           reply	other threads:[~2012-10-25 16:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5FBF8E85CA34454794F0F7ECBA79798F37A052B72B@HQMAIL04.nvidia.com>]

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=20121025164917.GR18814@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniels@nvidia.com \
    --cc=shaomingf@nvidia.com \
    --cc=swarren@nvidia.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.