iio: fix drivers that consider 0 as a valid IRQ in client->irq

Browse source

Since patch "i2c / ACPI: Use 0 to indicate that device does not have
interrupt assigned" [1], 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.

[1] http://lkml.kernel.org/g/<1430908148-201129-3-git-send-email-mika.westerberg@linux.intel.com>

Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>

...

This commit is contained in:

Octavian Purdila 2015-06-05 16:59:42 +03:00 • committed by Jonathan Cameron

parent d9abc615ea

commit c176becd81

4 changed files with 7 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

drivers/iio/accel/bmc150-accel.c

View file

2

drivers/iio/accel/kxcjk-1013.c

View file

2

drivers/iio/accel/mma9553.c

View file

8

drivers/iio/imu/kmx61.c

View file