From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "ext Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: "sakoman@gmail.com" <sakoman@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"getarunks@gmail.com" <getarunks@gmail.com>
Subject: Re: [PATCH 0/2] ASoC: TWL4030: DAPM restructuring and Headset pop-attenuation fix
Date: Tue, 19 May 2009 09:46:40 +0300 [thread overview]
Message-ID: <200905190946.40358.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03056A148C@dbde02.ent.ti.com>
On Monday 18 May 2009 18:28:52 ext Aggarwal, Anuj wrote:
> [Aggarwal, Anuj] I tried this on OMAP3 EVM. Ramp delay values 0-3 produces
> minor glitches in the beginning & end, value 4 gave me the best result so
> far on my EVM, I will try with some other EVMs as well before finalizing
> it. 5 and others produce a beep in the beginning and end. Just one
> question, is there any side-effect of choosing a large ramp delay? For e.g.
> in my case, it could be 437ms (19.2MHz clock).
It is less than half a second ;)
I'm not sure, but we could try later to add a timer to finish up the ramp-
down.
There could be (not foreseen) side effects...
At this point I think this (series) is a good start and it is better than what
we had.
BTW: I'll wait for the verdict on the series and I will send a fix for the
Handsfree pop attenuation also.
--
Péter
next prev parent reply other threads:[~2009-05-19 6:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 13:02 [PATCH 0/2] ASoC: TWL4030: DAPM restructuring and Headset pop-attenuation fix Peter Ujfalusi
2009-05-18 13:02 ` [PATCH 1/2] ASoC: TWL4030: Change DAPM routings and controls for DACs and PGAs Peter Ujfalusi
2009-05-18 13:02 ` [PATCH 2/2] ASoC: TWL4030: Move the Headset pop-attenuation code to PGA event Peter Ujfalusi
2009-05-18 13:09 ` [PATCH 0/2] ASoC: TWL4030: DAPM restructuring and Headset pop-attenuation fix Mark Brown
2009-05-18 15:28 ` Aggarwal, Anuj
2009-05-19 0:48 ` Lopez Cruz, Misael
2009-05-19 6:47 ` Aggarwal, Anuj
2009-05-19 8:00 ` Peter Ujfalusi
2009-05-19 8:30 ` Aggarwal, Anuj
2009-05-19 6:46 ` Peter Ujfalusi [this message]
2009-05-19 7:33 ` Jarkko Nikula
2009-05-19 18:58 ` Mark Brown
2009-05-20 5:56 ` Peter Ujfalusi
2009-05-20 8:21 ` Aggarwal, Anuj
2009-05-20 8:51 ` Mark Brown
2009-05-20 9:12 ` Peter Ujfalusi
2009-05-21 10:47 ` Aggarwal, Anuj
2009-05-21 11:06 ` Mark Brown
2009-05-20 9:08 ` Peter Ujfalusi
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=200905190946.40358.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=getarunks@gmail.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.