From: Mark Brown <broonie@kernel.org>
To: Dimitris Papavasiliou <dpapavas@gmail.com>
Cc: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: Need help fixing pop/click artifacts in an ASOC driver
Date: Wed, 14 Nov 2018 15:02:55 -0800 [thread overview]
Message-ID: <20181114230255.GG2089@sirena.org.uk> (raw)
In-Reply-To: <c0546298-960e-df17-273f-fa0734050aac@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1341 bytes --]
On Thu, Nov 15, 2018 at 12:50:30AM +0200, Dimitris Papavasiliou wrote:
> The clocks are switched inside the hw_params callback of the
> machine driver, when the sampling rate changes from a multiple of
> 48kHz to a multiple of 44.1kHz and vice versa, usually after
> opening the device and before starting playback. That has to be
> so, as far as I can see.
That's fairly normal, yes. You can also do SRC in software and lock the
rate at one.
> If by idle you mean, not playing, then the device is idle during
> the switch. If by idle you mean biased off, then it depends on
> circumstance. For instance if playback at 44.1kHz is stopped and
> quickly restarted at 48kHz, as often happens, the device won't
> have had the chance to sit long enough to be biased off (and even
> if it has, I'm not entirely sure whether it won't be biased on
> before the hw_params callback). The pop may still be avoided if
Usually it's only the digital that will notice clocking changes, so long
as none of the digital stuff is active you're normally fine. It does
depend on the hardware though.
> auto-mute is used, but that's not always the case. My proposed
> fix on the other hand consistently avoids generating the pop and
> does not rely on muting. I'm just not sure how to best implement
> it.
I've no idea what you're proposing, sorry.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-11-14 23:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 16:37 Need help fixing pop/click artifacts in an ASOC driver Dimitris Papavasiliou
2018-11-08 1:42 ` Pierre-Louis Bossart
2018-11-08 15:18 ` Takashi Iwai
2018-11-10 15:46 ` Dimitris Papavasiliou
2018-11-14 22:06 ` Mark Brown
2018-11-14 22:50 ` Dimitris Papavasiliou
2018-11-14 23:02 ` Mark Brown [this message]
2018-11-14 23:55 ` Dimitris Papavasiliou
2018-11-15 0:33 ` Mark Brown
2018-11-15 11:25 ` Dimitris Papavasiliou
2018-11-15 19:04 ` Mark Brown
2018-11-18 13:37 ` Dimitris Papavasiliou
2018-11-24 20:17 ` Dimitris Papavasiliou
2018-12-13 17:42 ` Mark Brown
2018-12-17 12:17 ` Dimitris Papavasiliou
2018-12-17 12:37 ` Mark Brown
2018-12-17 12:58 ` Dimitris Papavasiliou
2018-12-17 14:10 ` Mark Brown
2018-12-17 15:03 ` Dimitris Papavasiliou
2018-12-17 15:40 ` Mark Brown
2018-12-17 16:23 ` Dimitris Papavasiliou
2018-12-17 16:52 ` Mark Brown
2018-12-18 10:39 ` Dimitris Papavasiliou
2018-12-19 16:19 ` Mark Brown
2018-12-19 21:44 ` Dimitris Papavasiliou
2018-12-20 15:36 ` Mark Brown
2018-12-20 20:41 ` Dimitris Papavasiliou
2018-12-21 10:57 ` Mark Brown
2018-12-21 13:05 ` Dimitris Papavasiliou
2018-12-21 17:33 ` Mark Brown
2018-12-23 20:11 ` Dimitris Papavasiliou
2018-12-22 14:44 ` Matthias Reichl
2018-12-23 20:15 ` Dimitris Papavasiliou
2018-12-17 15:03 ` Pierre-Louis Bossart
2018-12-17 17:39 ` Mark Brown
2018-12-17 18:08 ` Pierre-Louis Bossart
2018-12-17 19:02 ` Mark Brown
2018-12-17 19:14 ` Pierre-Louis Bossart
2019-01-05 19:01 ` Pierre-Louis Bossart
2018-12-18 11:32 ` Dimitris Papavasiliou
2018-12-18 14:12 ` Pierre-Louis Bossart
2018-12-18 17:10 ` Dimitris Papavasiliou
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=20181114230255.GG2089@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dpapavas@gmail.com \
--cc=pierre-louis.bossart@linux.intel.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.