summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorMatt Ranostay <mranostay@gmail.com>2015-10-27 04:18:23 +0100
committerJonathan Cameron <jic23@kernel.org>2015-11-21 16:56:53 +0100
commit45a6b8218df54087c3bb8dc731424d8789d31790 (patch)
tree4807f065fc392f11cf68667c75244a398b2547c2 /include
parentstaging: iio: dummy: complete IIO events delivery to userspace (diff)
downloadlinux-45a6b8218df54087c3bb8dc731424d8789d31790.tar.xz
linux-45a6b8218df54087c3bb8dc731424d8789d31790.zip
iio: lidar: return -EINVAL on invalid signal
Returning zero from the measurment function has the side effect of corrupting the triggered buffer readings, better to use -EINVAL than a zero measurement reading. The INVALID status happens even it isn't out of range sometimes roughly once every second or two. This can be from an invalid second signal return path. Hence there are spurious zero readings from the triggered buffer, and warning messages in the kernel log. Signed-off-by: Matt Ranostay <mranostay@gmail.com> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions