From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: broonie@kernel.org, cw00.choi@samsung.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, perex@perex.cz, tiwai@suse.com,
stable@vger.kernel.org
Subject: Re: [PATCH] ASoC: arizona-jack: Fix runtime PM leak in arizona_start_mic()
Date: Fri, 18 Sep 2026 16:05:52 +0100 [thread overview]
Message-ID: <aq1TUA77ukvvBjso@opensource.cirrus.com> (raw)
In-Reply-To: <20260917164625.2163097-1-vulab@iscas.ac.cn>
On Thu, Sep 17, 2026 at 04:46:25PM +0000, Wentao Liang wrote:
> arizona_start_mic() takes a runtime PM reference before enabling mic
> detection, but the error path taken when regmap_update_bits_check()
> fails returns without releasing it, since pm_runtime_put_autosuspend()
> is only called in the !change branch. This leaks a runtime PM reference
> whenever the register write fails.
>
> Release the reference on the error path as well.
>
> Fixes: fbdc60b2a787 ("extcon: arizona: Correct error handling on regmap_update_bits_check")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> sound/soc/codecs/arizona-jack.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/soc/codecs/arizona-jack.c b/sound/soc/codecs/arizona-jack.c
> index a9063bac2752..09a100846fdb 100644
> --- a/sound/soc/codecs/arizona-jack.c
> +++ b/sound/soc/codecs/arizona-jack.c
> @@ -274,6 +274,7 @@ static void arizona_start_mic(struct arizona_priv *info)
> &change);
> if (ret < 0) {
> dev_err(arizona->dev, "Failed to enable micd: %d\n", ret);
> + pm_runtime_put_autosuspend(arizona->dev);
Not sure this one makes sense. The current approach appears to be
leave the mic stuff going and just log the error. If we wanted to
drop the runtime reference here there would be more teardown to
add, such as disabling the regulator. However, the micdet ena
failing likely means the buttons don't work on the headset, but
the mic record is probably still be working.
In general be a little careful with fixing these quite complex
processes this and the one from the other day on the
hpdet_acc_id() are scary things to be tweaking especially if
these issues are being spotted by some sort of AI/automated
tooling, and not tested on actual hardware.
Thanks,
Charles
prev parent reply other threads:[~2026-09-18 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 16:46 Wentao Liang
2026-09-18 15:05 ` Charles Keepax [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=aq1TUA77ukvvBjso@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=vulab@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®