iio: fix drivers that use 0 as a valid IRQ in client->irq (part 2)

Browse source

Since commit dab472eb93 ("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>

...

This commit is contained in:

Octavian Purdila 2015-09-23 12:02:00 +03:00 • committed by Jonathan Cameron

parent 1de953e77b

commit 6839c1b070

3 changed files with 3 additions and 3 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/stk8312.c

View file

2

drivers/iio/accel/stk8ba50.c

View file

2

drivers/iio/light/stk3310.c

View file