exynos-linux-stable/tools/iio
Bastien Nocera e2482f7649 iio: iio-utils: Fix possible incorrect mask calculation
[ Upstream commit 208a68c8393d6041a90862992222f3d7943d44d6 ]

On some machines, iio-sensor-proxy was returning all 0's for IIO sensor
values. It turns out that the bits_used for this sensor is 32, which makes
the mask calculation:

*mask = (1 << 32) - 1;

If the compiler interprets the 1 literals as 32-bit ints, it generates
undefined behavior depending on compiler version and optimization level.
On my system, it optimizes out the shift, so the mask value becomes

*mask = (1) - 1;

With a mask value of 0, iio-sensor-proxy will always return 0 for every axis.

Avoid incorrect 0 values caused by compiler optimization.

See original fix by Brett Dutro <brett.dutro@gmail.com> in
iio-sensor-proxy:
9615ceac7c

Signed-off-by: Bastien Nocera <hadess@hadess.net>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2019-08-04 09:33:38 +02:00
..
iio_event_monitor.c iio: Add channel for UV index 2016-04-03 11:14:01 +01:00
iio_generic_buffer.c tools:iio:iio_generic_buffer: fix trigger-less mode 2016-08-29 18:06:21 +01:00
iio_utils.c iio: iio-utils: Fix possible incorrect mask calculation 2019-08-04 09:33:38 +02:00
iio_utils.h iio: tools: generic_buffer: auto-enable channels 2016-04-19 19:58:13 +01:00
lsiio.c tools: iio: lsiio: enumerate processed channels 2016-08-15 18:33:23 +01:00
Makefile tools: iio: Rename generic_buffer to iio_generic_buffer 2016-05-29 19:56:33 +01:00