From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, david.rhodes@cirrus.com,
rf@opensource.cirrus.com, linux-sound@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] ASoC: cs42l43-jack: Remove manual pm_runtime get/put from tip_sense_work
Date: Mon, 16 Mar 2026 14:27:39 +0000 [thread overview]
Message-ID: <abgTWxI1Q9M1o+ka@opensource.cirrus.com> (raw)
In-Reply-To: <20260316124924.31047-1-peter.ujfalusi@linux.intel.com>
On Mon, Mar 16, 2026 at 02:49:24PM +0200, Peter Ujfalusi wrote:
> When a jack is inserted the forced pm_runtime_get() will keep the codec,
> soundwire bus and it's parent active as long as the jack is connected.
> This makes for example the DSP and firmware booted up on Intel platforms.
>
> If the module is removed while the jack is connected we will also have
> unbalanced runtime PM state.
>
> Without the manual get/put, the button detection still works correctly and
> the system can reach lower power state while the jack is connected like
> in the case when there is no jack connected.
>
> Fixes: fc918cbe874e ("ASoC: cs42l43: Add support for the cs42l43")
> Cc: stable@vger.kernel.org
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
> ---
> sound/soc/codecs/cs42l43-jack.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/sound/soc/codecs/cs42l43-jack.c b/sound/soc/codecs/cs42l43-jack.c
> index 3e04e6897b14..d90a13a55845 100644
> --- a/sound/soc/codecs/cs42l43-jack.c
> +++ b/sound/soc/codecs/cs42l43-jack.c
> @@ -756,10 +756,8 @@ void cs42l43_tip_sense_work(struct work_struct *work)
> ring = (sts >> CS42L43_RINGSENSE_PLUG_DB_STS_SHIFT) & CS42L43_JACK_PRESENT;
>
> if (tip == CS42L43_JACK_PRESENT) {
> - if (cs42l43->sdw && !priv->jack_present) {
> + if (cs42l43->sdw && !priv->jack_present)
> priv->jack_present = true;
> - pm_runtime_get(priv->dev);
> - }
Hmm... yes, I have this feeling this was in here for a reason I
should probably have left a comment here. I somewhat agree it
looks a bit mad with fresh eyes. The variable is also only used
for tracking this pm_runtime_get so you can drop the jack_present
variable from the struct as well, if we take the patch forward.
Best I can come up with was it was some interaction with the
Intel host's doing a bus reset when coming out of clock stop. I
think that might have caused something important to get
clobbered in some situations. But anyway will do some testing and
thinking and report back.
Thanks,
Charles
next prev parent reply other threads:[~2026-03-16 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 12:49 [PATCH] ASoC: cs42l43-jack: Remove manual pm_runtime get/put from tip_sense_work Peter Ujfalusi
2026-03-16 14:27 ` Charles Keepax [this message]
2026-03-16 14:37 ` Péter Ujfalusi
2026-03-16 16:40 ` Charles Keepax
2026-03-17 6:21 ` Péter Ujfalusi
2026-03-17 9:11 ` Péter Ujfalusi
2026-03-17 9:36 ` Péter Ujfalusi
2026-03-17 11:36 ` Charles Keepax
2026-03-17 11:44 ` Charles Keepax
2026-03-17 12:07 ` Péter Ujfalusi
2026-03-17 13:25 ` Charles Keepax
2026-03-16 14:58 ` Charles Keepax
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=abgTWxI1Q9M1o+ka@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=rf@opensource.cirrus.com \
--cc=stable@vger.kernel.org \
/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