From: sashiko-bot@kernel.org
To: phucduc.bui@gmail.com
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH 3/5] ASoC: fsl_asrc: Fix runtime PM usage count on init failure
Date: Thu, 12 Nov 2026 11:00:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-210984@kernel.org> (raw)
In-Reply-To: <20261112105116.32274-4-phucduc.bui@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] ASoC: fsl_asrc: wrong Fixes tag and pm_runtime_get_sync() in
commit msg
--
commit 503d1e3d04da11b4fe4bd7121c2929541b45d6b1
Author: bui duc phuc <phucduc.bui@gmail.com>
> ASoC: fsl_asrc: Fix runtime PM usage count on init failure
>
> Balance the runtime PM usage count when fsl_asrc_init() fails
> after pm_runtime_get_sync() succeeds.
>
> Fixes: 286d658477a4 ("ASoC: fsl_asrc: register m2m platform device")
> Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>
[Severity: Low]
Commit 286d658477a4 ("ASoC: fsl_asrc: register m2m platform device") only
added fsl_asrc_m2m_init() at the end of fsl_asrc_probe() and did not touch
fsl_asrc_init() or its error path. The unbalanced runtime PM usage count on
fsl_asrc_init() failure was introduced by commit cab04ab5900f ("ASoC:
fsl_asrc: Don't use devm_regmap_init_mmio_clk"), so the Fixes tag should
point to that commit instead.
Also, fsl_asrc_probe() acquires the reference via pm_runtime_resume_and_get()
rather than pm_runtime_get_sync() since commit d05040741afe ("ASoC: fsl_asrc:
using pm_runtime_resume_and_get to simplify the code").
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112105116.32274-1-phucduc.bui@gmail.com?part=3
next prev parent reply other threads:[~2026-11-12 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:51 [PATCH 0/5] ASoC: fsl_asrc: Fix probe and resource management issues phucduc.bui
2026-11-12 10:51 ` [PATCH 1/5] ASoC: fsl_asrc: Improve probe error handling phucduc.bui
2026-11-12 10:51 ` [PATCH 2/5] ASoC: fsl_asrc: Fix handling of deferred spba clock phucduc.bui
2026-11-12 10:57 ` sashiko-bot
2026-11-12 10:51 ` [PATCH 3/5] ASoC: fsl_asrc: Fix runtime PM usage count on init failure phucduc.bui
2026-11-12 11:00 ` sashiko-bot [this message]
2026-11-12 10:51 ` [PATCH 4/5] ASoC: fsl_asrc: Request the IRQ after the device is initialized phucduc.bui
2026-11-12 10:51 ` [PATCH 5/5] ASoC: fsl_asrc: Use devm for runtime PM cleanup phucduc.bui
2026-11-12 11:04 ` sashiko-bot
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=sashiko-outbox-210984@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=phucduc.bui@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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