On some boards interrupt type might be different than TRIGGER_FALLING,
like hardcoded in driver. Leave interrupt flags as they were pre-configured
from the device-tree.
Signed-off-by: Markuss Broks <markuss.broks@xxxxxxxxx>
---
drivers/iio/proximity/vl53l0x-i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/proximity/vl53l0x-i2c.c b/drivers/iio/proximity/vl53l0x-i2c.c
index 661a79ea200d..16f809c479cb 100644
--- a/drivers/iio/proximity/vl53l0x-i2c.c
+++ b/drivers/iio/proximity/vl53l0x-i2c.c
@@ -61,7 +61,7 @@ static int vl53l0x_configure_irq(struct i2c_client *client,
int ret;
ret = devm_request_irq(&client->dev, client->irq, vl53l0x_handle_irq,
- IRQF_TRIGGER_FALLING, indio_dev->name, indio_dev);
+ 0, indio_dev->name, indio_dev);
if (ret) {
dev_err(&client->dev, "devm_request_irq error: %d\n", ret);
return ret;
--
2.35.1
