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>

1 files changed, 1 insertions, 1 deletions

diff --git a/drivers/iio/accel/stk8ba50.c b/drivers/iio/accel/stk8ba50.c
index 80f77d8704b5..a59f5d87ae3a 100644
--- a/drivers/iio/accel/stk8ba50.c
+++ b/drivers/iio/accel/stk8ba50.c
@@ -468,7 +468,7 @@ static int stk8ba50_probe(struct i2c_client *client,
         if (client->irq < 0)
                 client->irq = stk8ba50_gpio_probe(client);
 
-        if (client->irq >= 0) {
+        if (client->irq > 0) {
                 ret = devm_request_threaded_irq(&client->dev, client->irq,
                                                 stk8ba50_data_rdy_trig_poll,
                                                 NULL,