[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20220902131340.3316479-1-cmo@melexis.com>
Date: Fri, 2 Sep 2022 15:13:40 +0200
From: cmo@...exis.com
To: Jonathan Cameron <jic23@...nel.org>
Cc: linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
Andy Shevchenko <andy.shevchenko@...il.com>,
Crt Mori <cmo@...exis.com>
Subject: [PATCH 3/3] iio: temperature: mlx90632 Change return value of sensor measurement channel
From: Crt Mori <cmo@...exis.com>
The current EINVAL value is more applicable to embedded library, where
user can actually put the fixed value to the sensor. In case of the
driver if the value of the channel is invalid it is better in inform
userspace that Channel was out of range as that implies more to internal
driver error than invalid input. It also makes for easier debugging of
where the error comes from during the development.
Signed-off-by: Crt Mori <cmo@...exis.com>
---
drivers/iio/temperature/mlx90632.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/temperature/mlx90632.c b/drivers/iio/temperature/mlx90632.c
index 63b19ac1484c..031aaa5493e8 100644
--- a/drivers/iio/temperature/mlx90632.c
+++ b/drivers/iio/temperature/mlx90632.c
@@ -439,7 +439,7 @@ static int mlx90632_channel_new_select(int perform_ret, uint8_t *channel_new,
*channel_old = 1;
break;
default:
- return -EINVAL;
+ return -ECHRNG;
}
return 0;
--
2.34.1
Powered by blists - more mailing lists