From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
ranjani.sridharan@linux.intel.com,
yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
daniel.baluta@nxp.com
Subject: [PATCH 0/7] ASoC: SOF: Use guard()/scoped_guard() for locks when makes sense
Date: Mon, 12 Jan 2026 12:09:57 +0200 [thread overview]
Message-ID: <20260112101004.7648-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
Only code refactoring, and no behavior change.
Replace most of the manual *lock/*unlock handling with guard use.
Regards,
Peter
---
Peter Ujfalusi (7):
ASoC: SOF: Use guard()/scoped_guard() for mutex locks where it makes
sense
ASoC: SOF: Intel: Use guard()/scoped_guard() for mutex locks where it
makes sense
ASoC: SOF: amd: acp-ipc: Use guard() for spinlock_irq()
ASoC: SOF: imx: imx-common: Use guard() for spinlock_irqsafe()
ASoC: SOF: mediatek: mtk-adsp-common: Use guard() for spinlock_irqsave
ASoC: SOF: Intel: Use guard() for spinlocks where it makes sense
ASoC: SOF: ipc/ops: Use guard() for spinlocks
sound/soc/sof/amd/acp-ipc.c | 4 +--
sound/soc/sof/imx/imx-common.c | 8 ++---
sound/soc/sof/intel/atom.c | 7 +---
sound/soc/sof/intel/bdw.c | 7 +---
sound/soc/sof/intel/cnl.c | 11 ++----
sound/soc/sof/intel/hda-dai-ops.c | 25 ++++++-------
sound/soc/sof/intel/hda-ipc.c | 11 ++----
sound/soc/sof/intel/hda-mlink.c | 29 +++++----------
sound/soc/sof/intel/hda-stream.c | 11 +++---
sound/soc/sof/intel/mtl.c | 5 +--
sound/soc/sof/ipc.c | 9 ++---
sound/soc/sof/ipc3-topology.c | 6 ++--
sound/soc/sof/ipc3.c | 8 ++---
sound/soc/sof/ipc4-mtrace.c | 24 +++++--------
sound/soc/sof/ipc4-pcm.c | 3 +-
sound/soc/sof/ipc4-topology.c | 5 +--
sound/soc/sof/ipc4.c | 8 ++---
sound/soc/sof/mediatek/mtk-adsp-common.c | 4 +--
sound/soc/sof/ops.c | 34 ++++--------------
sound/soc/sof/ops.h | 10 ++----
sound/soc/sof/sof-audio.c | 46 +++++++++---------------
sound/soc/sof/sof-client.c | 40 ++++++---------------
22 files changed, 95 insertions(+), 220 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-12 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 10:09 Peter Ujfalusi [this message]
2026-01-12 10:09 ` [PATCH 1/7] ASoC: SOF: Use guard()/scoped_guard() for mutex locks where it makes sense Peter Ujfalusi
2026-01-12 10:09 ` [PATCH 2/7] ASoC: SOF: Intel: " Peter Ujfalusi
2026-01-12 10:10 ` [PATCH 3/7] ASoC: SOF: amd: acp-ipc: Use guard() for spinlock_irq() Peter Ujfalusi
2026-01-12 10:10 ` [PATCH 4/7] ASoC: SOF: imx: imx-common: Use guard() for spinlock_irqsafe() Peter Ujfalusi
2026-01-12 10:10 ` [PATCH 5/7] ASoC: SOF: mediatek: mtk-adsp-common: Use guard() for spinlock_irqsave Peter Ujfalusi
2026-01-12 10:10 ` [PATCH 6/7] ASoC: SOF: Intel: Use guard() for spinlocks where it makes sense Peter Ujfalusi
2026-01-12 10:10 ` [PATCH 7/7] ASoC: SOF: ipc/ops: Use guard() for spinlocks Peter Ujfalusi
2026-01-13 13:49 ` [PATCH 0/7] ASoC: SOF: Use guard()/scoped_guard() for locks when makes sense 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=20260112101004.7648-1-peter.ujfalusi@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=yung-chuan.liao@linux.intel.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