iio: addac: ad74413r: Stop using iio_device_claim_direct_scoped()

This complex cleanup.h use case of conditional guards has proved
to be more trouble that it is worth in terms of false positive compiler
warnings and hard to read code.

Move directly to the new claim/release_direct() that allow sparse
to check for unbalanced context. Includes moving a mutex lock
into a function rather than around it to simplify the error handling.

Reviewed-by: David Lechner <dlechner@baylibre.com>
Reviewed-by: Nuno Sa <nuno.sa@analog.com>
Link: https://patch.msgid.link/20250209180624.701140-21-jic23@kernel.org
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

diff --git a/drivers/iio/addac/ad74413r.c b/drivers/iio/addac/ad74413r.c
index daea2bde7acf95211d705bfc6a86f754c82642e0..f14d12b03da6673443c479abaa66bee65670bbad 100644 (file)
--- a/drivers/iio/addac/ad74413r.c
+++ b/drivers/iio/addac/ad74413r.c
@@ -826,6 +826,8 @@ static int _ad74413r_get_single_adc_result(struct ad74413r_state *st,
        unsigned int uval;
        int ret;
 
+       guard(mutex)(&st->lock);
+
        reinit_completion(&st->adc_data_completion);
 
        ret = ad74413r_set_adc_channel_enable(st, channel, true);
@@ -865,12 +867,14 @@ static int ad74413r_get_single_adc_result(struct iio_dev *indio_dev,
                                          unsigned int channel, int *val)
 {
        struct ad74413r_state *st = iio_priv(indio_dev);
+       int ret;
 
-       iio_device_claim_direct_scoped(return -EBUSY, indio_dev) {
-               guard(mutex)(&st->lock);
-               return _ad74413r_get_single_adc_result(st, channel, val);
-       }
-       unreachable();
+       if (!iio_device_claim_direct(indio_dev))
+               return -EBUSY;
+
+       ret = _ad74413r_get_single_adc_result(st, channel, val);
+       iio_device_release_direct(indio_dev);
+       return ret;
 }
 
 static void ad74413r_adc_to_resistance_result(int adc_result, int *val)