[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8b96ad7e-5a47-458f-bb42-7b7c9efb82e1@web.de>
Date: Fri, 7 Feb 2025 17:35:49 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Laurentiu Mihalcea <laurentiu.mihalcea@....com>, imx@...ts.linux.dev,
linux-sound@...r.kernel.org, Bard Liao <yung-chuan.liao@...ux.intel.com>,
Daniel Baluta <daniel.baluta@....com>,
Iuliana Prodan <iuliana.prodan@....com>, Jaroslav Kysela <perex@...ex.cz>,
Mark Brown <broonie@...nel.org>, Takashi Iwai <tiwai@...e.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/7] ASoC: SOF: imx: introduce more common structures
and functions
…
> +++ b/sound/soc/sof/imx/imx-common.c
> @@ -1,11 +1,16 @@
…
> +static void imx_handle_reply(struct imx_dsp_ipc *ipc)
> +{
…
> + spin_lock_irqsave(&sdev->ipc_lock, flags);
> + snd_sof_ipc_process_reply(sdev, 0);
> + spin_unlock_irqrestore(&sdev->ipc_lock, flags);
> +}
…
Under which circumstances would you become interested to apply a statement
like “guard(spinlock_irqsave)(&sdev->ipc_lock);”?
https://elixir.bootlin.com/linux/v6.13.1/source/include/linux/spinlock.h#L572
Regards,
Markus
Powered by blists - more mailing lists