From: Jarkko Nikula <jhnikula@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: sakoman@gmail.com, anuj.aggarwal@ti.com,
alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
getarunks@gmail.com
Subject: Re: [PATCH 1/1] ASoC: TWL4030: Headset VMID ramp fix
Date: Fri, 8 May 2009 09:40:44 +0300 [thread overview]
Message-ID: <20090508094044.0c85e86a.jhnikula@gmail.com> (raw)
In-Reply-To: <1241763077-6851-2-git-send-email-peter.ujfalusi@nokia.com>
On Fri, 8 May 2009 09:11:17 +0300
Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:
> This patch fixes the 'tuck' phenomena observed on the headset
> output after the streams are stopped and DAPM send the codec
> to standby mode.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
> ---
> sound/soc/codecs/twl4030.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/codecs/twl4030.c b/sound/soc/codecs/twl4030.c
> index fd392c6..06042a1 100644
> --- a/sound/soc/codecs/twl4030.c
> +++ b/sound/soc/codecs/twl4030.c
> @@ -599,7 +599,7 @@ static int headsetl_event(struct
> snd_soc_dapm_widget *w, /* Is this needed? Can we just use whatever
> gain here? */ twl4030_write(w->codec, TWL4030_REG_HS_GAIN_SET,
> (hs_gain & (~0x0f)) | 0x0a);
> - hs_pop |= TWL4030_RAMP_EN;
> + hs_pop &= ~TWL4030_VMID_EN;
> twl4030_write(w->codec, TWL4030_REG_HS_POPN_SET,
> hs_pop);
> /* Restore the original volume */
> @@ -613,7 +613,7 @@ static int headsetl_event(struct
> snd_soc_dapm_widget *w, twl4030_i2c_write_u8
> (TWL4030_MODULE_AUDIO_VOICE, hs_gain & (~0x0f),
> TWL4030_REG_HS_GAIN_SET);
> - hs_pop &= ~TWL4030_VMID_EN;
> + hs_pop |= TWL4030_RAMP_EN;
> twl4030_write(w->codec, TWL4030_REG_HS_POPN_SET,
It really does fix the power-up & -down pops on Beagle. By listening
carefully I can hear slight power-up and -down pops but only if really
focusing on it.
But now the audio output is distorted and volume level is a little bit
lower. Without the patch it plays fine. Is it possible that now the
output voltage is not correctly biased? Worth to check with a scope.
--
Jarkko
next prev parent reply other threads:[~2009-05-08 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 6:11 [PATCH 0/1] ASoC: TWL4030: Possible fix for the Beep at the end of the audio file Peter Ujfalusi
2009-05-08 6:11 ` [PATCH 1/1] ASoC: TWL4030: Headset VMID ramp fix Peter Ujfalusi
2009-05-08 6:40 ` Jarkko Nikula [this message]
2009-05-08 11:56 ` Peter Ujfalusi
2009-05-08 12:14 ` Peter Ujfalusi
2009-05-08 12:34 ` Mark Brown
2009-05-08 12:32 ` Mark Brown
2009-05-08 12:39 ` Peter Ujfalusi
2009-05-08 13:55 ` Jarkko Nikula
2009-05-08 14:23 ` Jarkko Nikula
2009-05-11 6:22 ` Peter Ujfalusi
2009-05-11 9:36 ` Mark Brown
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=20090508094044.0c85e86a.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=getarunks@gmail.com \
--cc=peter.ujfalusi@nokia.com \
--cc=sakoman@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 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.