Bastien Nocera b150423e0d iio: iio-utils: Fix possible incorrect mask calculation ... [ Upstream commit 208a68c839 ] 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-07-31 07:27:02 +02:00
..
Build	iio: tools: move to tools buildsystem	2017-08-09 14:29:36 +01:00
iio_event_monitor.c	iio: Add modifier for DUV light	2018-07-23 19:18:10 +01:00
iio_generic_buffer.c	tools: iio: iio_generic_buffer: make num_loops signed	2019-02-15 08:10:10 +01:00
iio_utils.c	iio: iio-utils: Fix possible incorrect mask calculation	2019-07-31 07:27:02 +02:00
iio_utils.h	iio: tools: generic_buffer: increase trigger length	2017-05-07 16:08:04 +01:00
lsiio.c
Makefile	tools: fix cross-compile var clobbering	2018-02-21 15:35:42 -08:00