From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-sound@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH stable-6.6 0/2] ASoC: codecs: wsa883x: fix pops and clicks
Date: Thu, 23 Nov 2023 11:53:20 +0000 [thread overview]
Message-ID: <2023112313-handlebar-handwash-b263@gregkh> (raw)
In-Reply-To: <20231123094749.20462-1-johan+linaro@kernel.org>
On Thu, Nov 23, 2023 at 10:47:47AM +0100, Johan Hovold wrote:
> This is a backport of commits
>
> 0220575e65a ("ASoC: soc-dai: add flag to mute and unmute stream during trigger")
> 805ce81826c8 ("ASoC: codecs: wsa883x: make use of new mute_unmute_on_trigger flag")
>
> which specifically fix a loud crackling noise when starting a stream on
> the Lenovo ThinkPad X13s.
>
> These backports should apply to any stable tree which already has commit
> 3efcb471f871 ("ASoC: soc-pcm.c: Make sure DAI parameters cleared if the
> DAI becomes inactive") backported (e.g. 6.6.2 and 6.5.12).
>
> Note that the interaction of these commits resulted in a bad merge in
> mainline which is fixed up here:
>
> https://lore.kernel.org/lkml/20231123091815.21933-1-johan+linaro@kernel.org/
Thanks, now queued up.
greg k-h
prev parent reply other threads:[~2023-11-23 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 9:47 [PATCH stable-6.6 0/2] ASoC: codecs: wsa883x: fix pops and clicks Johan Hovold
2023-11-23 9:47 ` [PATCH stable-6.6 1/2] ASoC: soc-dai: add flag to mute and unmute stream during trigger Johan Hovold
2023-11-23 9:47 ` [PATCH stable-6.6 2/2] ASoC: codecs: wsa883x: make use of new mute_unmute_on_trigger flag Johan Hovold
2023-11-23 11:53 ` Greg Kroah-Hartman [this message]
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=2023112313-handlebar-handwash-b263@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sashal@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox