From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: alsa-devel@alsa-project.org
Cc: ext Mark Brown <broonie@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 2/2] ASoC: Do DAPM control updates in the middle of DAPM sequences
Date: Thu, 16 Dec 2010 15:51:13 +0200 [thread overview]
Message-ID: <201012161551.13096.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <1292349202-25538-2-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tuesday 14 December 2010 19:53:22 ext Mark Brown wrote:
> Attempt to minimise audible effects from mixer and mux updates by
> implementing the actual register changes between powering down widgets
> that have become unused and powering up widgets that are newly used.
>
> This means that we're making the change with the minimum set of widgets
> powered, that the input path is connected when we're powering up widgets
> (so things like DC offset correction can run with their signal active)
> and that we bring things down to cold before switching away. Since
> hardware tends to be designed for the power on/off case more than for
> dynamic reconfiguration this should minimise pops and clicks during
> reconfiguration while active.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>
> Peter, I think this will address your widget reordering issue - I'd
> appreciate it if you could test and let me know if it helps. If this
> works it avoids the need for the the widget to know anything about the
> particular algorithm implemented by DAPM which seems more robust to me.
>
> Sorry about how long it took to get this done.
Well, it is good, and bad.
It behaves mostly OK, but there's a strange side effect:
I noticed a pop on playback stream start on the twl4030 codec.
I'll look into it, but I do not see how this patch can affect the stream start..
Could you hold this patch for some time, so I can look at this?
Thanks,
Péter
next prev parent reply other threads:[~2010-12-16 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 17:53 [PATCH 1/2] ASoC: Remove unused DAPM_DOUBLE control types Mark Brown
2010-12-14 17:53 ` [PATCH 2/2] ASoC: Do DAPM control updates in the middle of DAPM sequences Mark Brown
2010-12-16 8:39 ` Peter Ujfalusi
2010-12-16 13:03 ` Peter Ujfalusi
2010-12-16 13:51 ` Peter Ujfalusi [this message]
2010-12-16 13:55 ` Mark Brown
2010-12-17 7:08 ` Peter Ujfalusi
2010-12-17 11:45 ` Mark Brown
2010-12-15 13:37 ` [PATCH 1/2] ASoC: Remove unused DAPM_DOUBLE control types Liam Girdwood
2010-12-15 18:10 ` 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=201012161551.13096.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox