iio: fix drivers that use 0 as a valid IRQ in client->irq (part 2)
authorOctavian Purdila <octavian.purdila@intel.com>
Wed, 23 Sep 2015 09:02:00 +0000 (12:02 +0300)
committerJonathan Cameron <jic23@kernel.org>
Sat, 3 Oct 2015 10:02:37 +0000 (11:02 +0100)
commit6839c1b0700a79375639528985a0ec0fbd58cf9a
tree20c57a55143274a9a8886d73cd7ae2c705f2e3be
parent1de953e77b8c8b8cb6f734733cf20e95a1b0fbb8
iio: fix drivers that use 0 as a valid IRQ in client->irq (part 2)

Since commit dab472eb931bc291 ("i2c / ACPI: Use 0 to indicate that
device does not have interrupt assigned") 0 is not a valid i2c
client irq anymore, so change all driver's checks accordingly.

The same issue occurs when the device is instantiated via device tree
with no IRQ, or from the i2c sysfs interface, even before the patch
above.

Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
drivers/iio/accel/stk8312.c
drivers/iio/accel/stk8ba50.c
drivers/iio/light/stk3310.c