ASoC: hisilicon: Use guard() for spin locks
PATCH 1/1 ASoC: hisilicon: Use guard() for spin locks
From: bui duc phuc <[email protected]>
Clean up the code using guard() for spin locks.
Merely code refactoring, and no behavior change.
--- sound/soc/hisilicon/hi6210-i2s.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
sound/soc/hisilicon/hi6210-i2s.c +2 -4
@@ -185,7 +185,7 @@ static void hi6210_i2s_txctrl(struct snd_soc_dai *cpu_dai, int on)struct hi6210_i2s *i2s =dev_get_drvdata (cpu_dai->dev);u32 val; -spin_lock (&i2s->lock); +guard (spinlock)(&i2s->lock);if (on) {/* enable S2 TX */ val =hi6210_read_reg (i2s,HII2S_I2S_CFG );
@@ -197,7 +197,6 @@ static void hi6210_i2s_txctrl(struct snd_soc_dai *cpu_dai, int on) val &= ~HII2S_I2S_CFG__S2_IF_TX_EN ;hi6210_write_reg (i2s,HII2S_I2S_CFG , val); } -spin_unlock (&i2s->lock); }static void hi6210_i2s_rxctrl (struct snd_soc_dai *cpu_dai,int on)
@@ -205,7 +204,7 @@ static void hi6210_i2s_rxctrl(struct snd_soc_dai *cpu_dai, int on)struct hi6210_i2s *i2s =dev_get_drvdata (cpu_dai->dev);u32 val; -spin_lock (&i2s->lock); +guard (spinlock)(&i2s->lock);if (on) { val =hi6210_read_reg (i2s,HII2S_I2S_CFG ); val |=HII2S_I2S_CFG__S2_IF_RX_EN ;
@@ -215,7 +214,6 @@ static void hi6210_i2s_rxctrl(struct snd_soc_dai *cpu_dai, int on) val &= ~HII2S_I2S_CFG__S2_IF_RX_EN ;hi6210_write_reg (i2s,HII2S_I2S_CFG , val); } -spin_unlock (&i2s->lock); }static int hi6210_i2s_set_fmt (struct snd_soc_dai *cpu_dai,unsigned int fmt)
Signature · 1 line
2.43.0
Mark Brown
maintainerQuoted 1 line · On Fri, 12 Jun 2026 19:31:50 +0700, [email protected] wrote:
ASoC: hisilicon: Use
guard()for spin locks
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.2
Thanks!
[1/1] ASoC: hisilicon: Use guard() for spin locks
https://git.kernel.org/broonie/sound/c/da6899fc88e4
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark