From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
stable@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] ASoC: soc-dai: add flag to mute and unmute stream during trigger.
Date: Wed, 22 Nov 2023 16:35:17 +0000 [thread overview]
Message-ID: <2023112225-crop-uncle-9097@gregkh> (raw)
In-Reply-To: <ZV4hMR8oGQBSbnMl@hovoldconsulting.com>
On Wed, Nov 22, 2023 at 04:41:37PM +0100, Johan Hovold wrote:
> Hi Greg and Sasha,
>
> On Fri, Oct 27, 2023 at 01:52:11PM +0200, Johan Hovold wrote:
> > On Fri, Oct 27, 2023 at 11:57:45AM +0100, Srinivas Kandagatla wrote:
> > > Click/Pop Noise was a long pending issue with WSA Codecs which are prone
> > > to accumlate DC when ports are active but without any data streams.
> > > There are multiple places in the current setup, where this could happen
> > > in both startup as well as shutdown path.
> > >
> > > This patchset adds a new flag mute_unmute_on_trigger to dai_ops to let
> > > generic code do the mute/unmute on trigger.
> > >
> > > This patches help fix those issues by making sure the PA is Muted/Unmuted
> > > inline with the stream start/stop events.
> > >
> > > Srinivas Kandagatla (2):
> > > ASoC: soc-dai: add flag to mute and unmute stream during trigger
> > > ASoC: codecs: wsa883x: make use of new mute_unmute_on_trigger flag
> >
> > I've verified that this fixes the pop sounds when starting and stopping
> > a stream on the X13s, even if the click sound when killing pulseaudio
> > (e.g. on reboot) is still there (as with the previous fixes).
> >
> > Tested-by: Johan Hovold <johan+linaro@kernel.org>
> >
> > If these are accepted, can we get them backported to 6.5 as well?
>
> These fixes are now in 6.7-rc1 as
>
> f0220575e65a ("ASoC: soc-dai: add flag to mute and unmute stream during trigger")
This doesn't backport cleanly, can you provide a working backport?
> 805ce81826c8 ("ASoC: codecs: wsa883x: make use of new mute_unmute_on_trigger flag")
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-11-22 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 10:57 [RFC PATCH 0/2] ASoC: soc-dai: add flag to mute and unmute stream during trigger Srinivas Kandagatla
2023-10-27 10:57 ` [RFC PATCH 1/2] " Srinivas Kandagatla
2023-10-27 10:57 ` [RFC PATCH 2/2] ASoC: codecs: wsa883x: make use of new mute_unmute_on_trigger flag Srinivas Kandagatla
2023-10-27 11:52 ` [RFC PATCH 0/2] ASoC: soc-dai: add flag to mute and unmute stream during trigger Johan Hovold
2023-11-22 15:41 ` Johan Hovold
2023-11-22 16:35 ` Greg Kroah-Hartman [this message]
2023-11-22 16:46 ` Greg Kroah-Hartman
2023-11-22 16:49 ` Johan Hovold
2023-11-23 9:54 ` Johan Hovold
2023-11-27 8:34 ` Johan Hovold
2023-10-27 12:00 ` Amadeusz Sławiński
2023-10-27 12:12 ` Johan Hovold
2023-10-27 22:54 ` 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=2023112225-crop-uncle-9097@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=johan@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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