From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Ziyi Guo <n7l8m4@u.northwestern.edu>,
Simon Trimmer <simont@opensource.cirrus.com>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: patches@opensource.cirrus.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] firmware: cs_dsp: fix missing pwr_lock in cs_dsp_stop()
Date: Mon, 2 Feb 2026 14:56:32 +0000 [thread overview]
Message-ID: <643cb846-ffbe-471b-b805-48a8401e4b01@opensource.cirrus.com> (raw)
In-Reply-To: <20260202144153.1668326-1-n7l8m4@u.northwestern.edu>
On 02/02/2026 2:41 pm, Ziyi Guo wrote:
> cs_dsp_signal_event_controls() calls cs_dsp_coeff_write_acked_control()
> which has lockdep_assert_held(&dsp->pwr_lock), but the lock is not held.
>
> cs_dsp_signal_event_controls() is invoked from cs_dsp_stop().
>
> Put mutex_lock() at the top of cs_dsp_stop() to fix the
> missing lock protection, also align with cs_dsp_run().
>
> Signed-off-by: Ziyi Guo <n7l8m4@u.northwestern.edu>
> ---
> v2:
> - Put mutex_lock() at the top of cs_dsp_stop() to fix and align with cs_dsp_run()
>
> drivers/firmware/cirrus/cs_dsp.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/cirrus/cs_dsp.c b/drivers/firmware/cirrus/cs_dsp.c
> index 525ac0f0a75d..a491e89c0c97 100644
> --- a/drivers/firmware/cirrus/cs_dsp.c
> +++ b/drivers/firmware/cirrus/cs_dsp.c
> @@ -2864,6 +2864,8 @@ EXPORT_SYMBOL_NS_GPL(cs_dsp_run, "FW_CS_DSP");
> */
> void cs_dsp_stop(struct cs_dsp *dsp)
> {
> + mutex_lock(&dsp->pwr_lock);
> +
> /* Tell the firmware to cleanup */
> cs_dsp_signal_event_controls(dsp, CS_DSP_FW_EVENT_SHUTDOWN);
>
> @@ -2874,7 +2876,6 @@ void cs_dsp_stop(struct cs_dsp *dsp)
> if (dsp->ops->show_fw_status)
> dsp->ops->show_fw_status(dsp);
>
> - mutex_lock(&dsp->pwr_lock);
>
> if (dsp->client_ops->pre_stop)
> dsp->client_ops->pre_stop(dsp);
Nitpick: Commit title "fix missing pwr_lock in cs_dsp_stop()", it's
not missing. Just in the wrong place.
Apart from that:
Reviewed-by: Richard Fitzgerald <rf@opensource.cirrus.com>
next prev parent reply other threads:[~2026-02-02 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 14:41 Ziyi Guo
2026-02-02 14:56 ` Richard Fitzgerald [this message]
2026-02-27 10:03 ` Richard Fitzgerald
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=643cb846-ffbe-471b-b805-48a8401e4b01@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n7l8m4@u.northwestern.edu \
--cc=patches@opensource.cirrus.com \
--cc=simont@opensource.cirrus.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
all inboxes | Powered by JetHome®