android_kernel_oneplus_msm8998/tools/iio
Bastien Nocera 623c3a6261 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:34:57 +02:00
..
generic_buffer.c iio: generic_buffer: be helpful about enabling channels 2015-08-16 10:51:26 +01:00
iio_event_monitor.c iio: event_monitor: report unsupported events 2015-08-16 10:51:25 +01:00
iio_utils.c iio: iio-utils: Fix possible incorrect mask calculation 2019-08-04 09:34:57 +02:00
iio_utils.h tools: iio: remove unnecessary double pointer 2015-08-08 19:54:00 +01:00
lsiio.c iio: lsiio: fix error code handling error 2015-08-12 19:26:22 +01:00
Makefile iio: make tools more cross-compilation friendly 2015-05-10 20:31:45 +01:00