From: Ethan Tidmore <ethantidmore06@gmail.com>
To: jic23@kernel.org
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Ethan Tidmore <ethantidmore06@gmail.com>
Subject: [PATCH v3 1/2] iio: light: gp2ap020a00f: simplify locking with guard()
Date: Sun, 15 Feb 2026 18:53:16 -0600 [thread overview]
Message-ID: <20260216005317.11763-2-ethantidmore06@gmail.com> (raw)
In-Reply-To: <20260216005317.11763-1-ethantidmore06@gmail.com>
Use the guard() cleanup handler to manage the device lock.
This simplifies the code by removing the need for manual unlocking
and goto error handling paths.
Suggested-by: Jonathan Cameron <jic23@kernel.org>
Signed-off-by: Ethan Tidmore <ethantidmore06@gmail.com>
---
v3:
- Use guard() instead of manual locking and unlocking.
drivers/iio/light/gp2ap020a00f.c | 64 ++++++++++----------------------
1 file changed, 20 insertions(+), 44 deletions(-)
diff --git a/drivers/iio/light/gp2ap020a00f.c b/drivers/iio/light/gp2ap020a00f.c
index c7df4b258e2c..d1a511ac7690 100644
--- a/drivers/iio/light/gp2ap020a00f.c
+++ b/drivers/iio/light/gp2ap020a00f.c
@@ -31,6 +31,7 @@
* the other one.
*/
+#include <linux/cleanup.h>
#include <linux/debugfs.h>
#include <linux/delay.h>
#include <linux/i2c.h>
@@ -1024,17 +1025,14 @@ static int gp2ap020a00f_write_event_val(struct iio_dev *indio_dev,
bool event_en = false;
u8 thresh_val_id;
u8 thresh_reg_l;
- int err = 0;
- mutex_lock(&data->lock);
+ guard(mutex)(&data->lock);
thresh_reg_l = gp2ap020a00f_get_thresh_reg(chan, dir);
thresh_val_id = GP2AP020A00F_THRESH_VAL_ID(thresh_reg_l);
- if (thresh_val_id > GP2AP020A00F_THRESH_PH) {
- err = -EINVAL;
- goto error_unlock;
- }
+ if (thresh_val_id > GP2AP020A00F_THRESH_PH)
+ return -EINVAL;
switch (thresh_reg_l) {
case GP2AP020A00F_TH_L_REG:
@@ -1046,30 +1044,23 @@ static int gp2ap020a00f_write_event_val(struct iio_dev *indio_dev,
&data->flags);
break;
case GP2AP020A00F_PH_L_REG:
- if (val == 0) {
- err = -EINVAL;
- goto error_unlock;
- }
+ if (val == 0)
+ return -EINVAL;
+
event_en = test_bit(GP2AP020A00F_FLAG_PROX_RISING_EV,
&data->flags);
break;
case GP2AP020A00F_PL_L_REG:
- if (val == 0) {
- err = -EINVAL;
- goto error_unlock;
- }
+ if (val == 0)
+ return -EINVAL;
+
event_en = test_bit(GP2AP020A00F_FLAG_PROX_FALLING_EV,
&data->flags);
break;
}
data->thresh_val[thresh_val_id] = val;
- err = gp2ap020a00f_write_event_threshold(data, thresh_val_id,
- event_en);
-error_unlock:
- mutex_unlock(&data->lock);
-
- return err;
+ return gp2ap020a00f_write_event_threshold(data, thresh_val_id, event_en);
}
static int gp2ap020a00f_read_event_val(struct iio_dev *indio_dev,
@@ -1081,23 +1072,17 @@ static int gp2ap020a00f_read_event_val(struct iio_dev *indio_dev,
{
struct gp2ap020a00f_data *data = iio_priv(indio_dev);
u8 thresh_reg_l;
- int err = IIO_VAL_INT;
- mutex_lock(&data->lock);
+ guard(mutex)(&data->lock);
thresh_reg_l = gp2ap020a00f_get_thresh_reg(chan, dir);
- if (thresh_reg_l > GP2AP020A00F_PH_L_REG) {
- err = -EINVAL;
- goto error_unlock;
- }
+ if (thresh_reg_l > GP2AP020A00F_PH_L_REG)
+ return -EINVAL;
*val = data->thresh_val[GP2AP020A00F_THRESH_VAL_ID(thresh_reg_l)];
-error_unlock:
- mutex_unlock(&data->lock);
-
- return err;
+ return IIO_VAL_INT;
}
static int gp2ap020a00f_write_prox_event_config(struct iio_dev *indio_dev,
@@ -1165,7 +1150,7 @@ static int gp2ap020a00f_write_event_config(struct iio_dev *indio_dev,
enum gp2ap020a00f_cmd cmd;
int err;
- mutex_lock(&data->lock);
+ guard(mutex)(&data->lock);
switch (chan->type) {
case IIO_PROXIMITY:
@@ -1186,8 +1171,6 @@ static int gp2ap020a00f_write_event_config(struct iio_dev *indio_dev,
err = -EINVAL;
}
- mutex_unlock(&data->lock);
-
return err;
}
@@ -1199,7 +1182,7 @@ static int gp2ap020a00f_read_event_config(struct iio_dev *indio_dev,
struct gp2ap020a00f_data *data = iio_priv(indio_dev);
int event_en = 0;
- mutex_lock(&data->lock);
+ guard(mutex)(&data->lock);
switch (chan->type) {
case IIO_PROXIMITY:
@@ -1223,8 +1206,6 @@ static int gp2ap020a00f_read_event_config(struct iio_dev *indio_dev,
break;
}
- mutex_unlock(&data->lock);
-
return event_en;
}
@@ -1385,7 +1366,7 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
struct gp2ap020a00f_data *data = iio_priv(indio_dev);
int i, err = 0;
- mutex_lock(&data->lock);
+ guard(mutex)(&data->lock);
/*
* Enable triggers according to the scan_mask. Enabling either
@@ -1413,15 +1394,12 @@ static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
}
if (err < 0)
- goto error_unlock;
+ return err;
data->buffer = kmalloc(indio_dev->scan_bytes, GFP_KERNEL);
if (!data->buffer)
err = -ENOMEM;
-error_unlock:
- mutex_unlock(&data->lock);
-
return err;
}
@@ -1430,7 +1408,7 @@ static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
struct gp2ap020a00f_data *data = iio_priv(indio_dev);
int i, err = 0;
- mutex_lock(&data->lock);
+ guard(mutex)(&data->lock);
iio_for_each_active_channel(indio_dev, i) {
switch (i) {
@@ -1452,8 +1430,6 @@ static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
if (err == 0)
kfree(data->buffer);
- mutex_unlock(&data->lock);
-
return err;
}
--
2.53.0
next prev parent reply other threads:[~2026-02-16 0:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 0:53 [PATCH v3 0/2] iio: light: gp2ap020a00f: fix return type and simplify locking Ethan Tidmore
2026-02-16 0:53 ` Ethan Tidmore [this message]
2026-02-16 7:08 ` [PATCH v3 1/2] iio: light: gp2ap020a00f: simplify locking with guard() Andy Shevchenko
2026-02-16 21:04 ` Ethan Tidmore
2026-02-17 8:37 ` Andy Shevchenko
2026-02-17 9:02 ` Ethan Tidmore
2026-02-17 9:12 ` Andy Shevchenko
2026-02-17 9:03 ` Andy Shevchenko
2026-02-17 9:10 ` Ethan Tidmore
2026-02-17 10:23 ` Andy Shevchenko
2026-02-16 0:53 ` [PATCH v3 2/2] iio: light: gp2ap020a00f: correct return type to int Ethan Tidmore
2026-02-16 7:10 ` Andy Shevchenko
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=20260216005317.11763-2-ethantidmore06@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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