From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: core: Allow digital mute for capture
Date: Thu, 7 Feb 2013 05:34:47 -0800 [thread overview]
Message-ID: <20130207133447.GQ3143@intel.com> (raw)
In-Reply-To: <1360173556-28048-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Wed, Feb 06, 2013 at 05:59:16PM +0000, Mark Brown wrote:
> Help avoid noise from the power up of the capture path propagating through
> into the start of the recording (especially noise caused by the ramp of
> microphone biases) by keeping the capture muted until after we've finished
> powering things up with DAPM in the same manner we do for playback. This
> allows us to take advantage of soft mute support in the hardware more
> effectively and is more consistent.
>
> The core code using the existing digital mute operation is updated to take
> advantage of this. Some additional cases in the soc-pcm code and suspend
> will need separate handling but these are less practically relevant than
> the main runtime stream start/stop case.
>
> Rather than refactor the digital mute function in every single driver a
> new operation is added for drivers taking advantage of this functionality,
> the old operation should be phased out over time.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by Vinod Koul <vinod.koul@intel.com>
prev parent reply other threads:[~2013-02-07 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 17:59 [PATCH] ASoC: core: Allow digital mute for capture Mark Brown
2013-02-07 13:34 ` Vinod Koul [this message]
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=20130207133447.GQ3143@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).