From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: perex@perex.cz, tiwai@suse.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
johan+linaro@kernel.org, steev@kali.org,
dmitry.baryshkov@linaro.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH 3/4] ASoC: codecs: wsa883x: mute/unmute PA in correct sequence
Date: Wed, 25 Oct 2023 09:57:12 +0200 [thread overview]
Message-ID: <ZTjKWHAAfSYfc5px@hovoldconsulting.com> (raw)
In-Reply-To: <2a0aabf5-41a3-cc07-3203-9b0bca6b71aa@linaro.org>
Hi Mark,
On Fri, Mar 24, 2023 at 06:44:40AM +0000, Srinivas Kandagatla wrote:
> On 23/03/2023 17:07, Mark Brown wrote:
> > On Thu, Mar 23, 2023 at 04:44:02PM +0000, Srinivas Kandagatla wrote:
> >> In the current setup the PA is left unmuted even when the
> >> Soundwire ports are not started streaming. This can lead to click
> >> and pop sounds during start.
> >> There is a same issue in the reverse order where in the PA is
> >> left unmute even after the data stream is stopped, the time
> >> between data stream stopping and port closing is long enough
> >> to accumulate DC on the line resulting in Click/Pop noise
> >> during end of stream.
> >
> > Wow, that hardware sounds *super* fragile.
> >
> >> Moving the mute/unmute to trigger stop/start respectively seems to
> >> help a lot with this Click/Pop issues reported on this Codec.
> >
> >> +static int wsa883x_trigger(struct snd_pcm_substream *s, int cmd,
> >> + struct snd_soc_dai *dai)
> >> +{
> >> + switch (cmd) {
> >> + case SNDRV_PCM_TRIGGER_START:
> >> + case SNDRV_PCM_TRIGGER_RESUME:
> >> + case SNDRV_PCM_TRIGGER_PAUSE_RELEASE:
> >> + wsa883x_digital_mute(dai, false, 0);
> >> + break;
> >
> >> static const struct snd_soc_dai_ops wsa883x_dai_ops = {
> >> + .startup = wsa883x_startup,
> >> .hw_params = wsa883x_hw_params,
> >> .hw_free = wsa883x_hw_free,
> >> - .mute_stream = wsa883x_digital_mute,
> >> + .trigger = wsa883x_trigger,
> > This feels like we should be doing it at the framework level, either
> > tightening up where the mute happens in general or having some option
> > that devices can select if they really need it.
> That makes more sense, I can give that a try.
I understand Srini has looked at this but has not yet been able to come
up with a generic implementation. Would it be possible to merge the two
codec fixes as an interim workaround for 6.7?
Without the wsa883x patch there's a loud crackling scary noise when
starting a stream on the Lenovo ThinkPad X13s which users will hit now
that they can run mainline on this machine.
https://lore.kernel.org/lkml/20230323164403.6654-4-srinivas.kandagatla@linaro.org/
I've been using this one myself for the past seven months without any
issues (even if there's still a faint click when stopping a stream):
Tested-by: Johan Hovold <johan+linaro@kernel.org>
Getting this backported at least to 6.5 where sound support for the X13s
was added would be great too.
Johan
next prev parent reply other threads:[~2023-10-25 8:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 16:43 [PATCH 0/4] ASoC: qcom: fixes for Click/Pop Noise Srinivas Kandagatla
2023-03-23 16:43 ` Srinivas Kandagatla
2023-03-23 16:44 ` [PATCH 1/4] ASoC: qcom: q6apm-lpass-dai: close graphs before opening a new one Srinivas Kandagatla
2023-03-23 16:44 ` Srinivas Kandagatla
2023-03-23 16:44 ` [PATCH 2/4] ASoC: qcom: sdw: do not restart soundwire ports for every prepare Srinivas Kandagatla
2023-03-23 16:44 ` Srinivas Kandagatla
2023-03-23 16:44 ` [PATCH 3/4] ASoC: codecs: wsa883x: mute/unmute PA in correct sequence Srinivas Kandagatla
2023-03-23 16:44 ` Srinivas Kandagatla
2023-03-23 17:07 ` Mark Brown
2023-03-23 17:07 ` Mark Brown
2023-03-23 18:11 ` Pierre-Louis Bossart
2023-03-24 0:14 ` Mark Brown
2023-03-24 6:43 ` Srinivas Kandagatla
2023-03-24 6:44 ` Srinivas Kandagatla
2023-03-24 6:44 ` Srinivas Kandagatla
2023-10-25 7:57 ` Johan Hovold [this message]
2023-10-25 12:36 ` Mark Brown
2023-10-25 12:43 ` Johan Hovold
2023-10-26 13:05 ` Mark Brown
2023-10-26 13:55 ` Johan Hovold
2023-10-27 10:51 ` Srinivas Kandagatla
2023-03-23 16:44 ` [PATCH 4/4] ASoC: codecs: wsa881x: " Srinivas Kandagatla
2023-03-23 16:44 ` Srinivas Kandagatla
2023-04-06 15:03 ` (subset) [PATCH 0/4] ASoC: qcom: fixes for Click/Pop Noise Mark Brown
2023-04-06 15:03 ` 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=ZTjKWHAAfSYfc5px@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=steev@kali.org \
--cc=tiwai@suse.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.