iio: light: bh1745: 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.

Reviewed-by: Mudit Sharma <muditsharma.info@gmail.com>
Reviewed-by: David Lechner <dlechner@baylibre.com>
Link: https://patch.msgid.link/20250209180624.701140-27-jic23@kernel.org
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

diff --git a/drivers/iio/light/bh1745.c b/drivers/iio/light/bh1745.c
index 3b4056be54a03ce76282c9dceb440dd94224d2a5..56ab5fe90ff9128035cf25948bba1589492e66e4 100644 (file)
--- a/drivers/iio/light/bh1745.c
+++ b/drivers/iio/light/bh1745.c
@@ -426,16 +426,16 @@ static int bh1745_read_raw(struct iio_dev *indio_dev,
 
        switch (mask) {
        case IIO_CHAN_INFO_RAW:
-               iio_device_claim_direct_scoped(return -EBUSY, indio_dev) {
-                       ret = regmap_bulk_read(data->regmap, chan->address,
-                                              &value, 2);
-                       if (ret)
-                               return ret;
-                       *val = value;
+               if (!iio_device_claim_direct(indio_dev))
+                       return -EBUSY;
 
-                       return IIO_VAL_INT;
-               }
-               unreachable();
+               ret = regmap_bulk_read(data->regmap, chan->address, &value, 2);
+               iio_device_release_direct(indio_dev);
+               if (ret)
+                       return ret;
+               *val = value;
+
+               return IIO_VAL_INT;
 
        case IIO_CHAN_INFO_SCALE: {
                        guard(mutex)(&data->lock);