Input: pwm-beeper - use guard notation when acquiring spinlock

Using guard notation makes the code more compact and error handling
more robust by ensuring that locks are released in all code paths
when control leaves critical section.

Reviewed-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Link: https://lore.kernel.org/r/20240904044914.1049280-1-dmitry.torokhov@gmail.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

diff --git a/drivers/input/misc/pwm-beeper.c b/drivers/input/misc/pwm-beeper.c
index 5b9aedf..0e19e97 100644 (file)
--- a/drivers/input/misc/pwm-beeper.c
+++ b/drivers/input/misc/pwm-beeper.c
@@ -203,9 +203,9 @@ static int pwm_beeper_suspend(struct device *dev)
         * beeper->suspended, but to ensure that pwm_beeper_event
         * does not re-submit work once flag is set.
         */
-       spin_lock_irq(&beeper->input->event_lock);
-       beeper->suspended = true;
-       spin_unlock_irq(&beeper->input->event_lock);
+       scoped_guard(spinlock_irq, &beeper->input->event_lock) {
+               beeper->suspended = true;
+       }
 
        pwm_beeper_stop(beeper);
 
@@ -216,9 +216,9 @@ static int pwm_beeper_resume(struct device *dev)
 {
        struct pwm_beeper *beeper = dev_get_drvdata(dev);
 
-       spin_lock_irq(&beeper->input->event_lock);
-       beeper->suspended = false;
-       spin_unlock_irq(&beeper->input->event_lock);
+       scoped_guard(spinlock_irq, &beeper->input->event_lock) {
+               beeper->suspended = false;
+       }
 
        /* Let worker figure out if we should resume beeping */
        schedule_work(&beeper->work);