summaryrefslogtreecommitdiffstats
path: root/drivers/iio/imu/adis_trigger.c
diff options
context:
space:
mode:
authorNuno Sá <nuno.sa@analog.com>2021-09-03 16:14:20 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2021-10-19 08:27:34 +0100
commit31fa357ac809affd9f9a7d0b5d1991951e16beec (patch)
treed3e73050dea1fe8ddf157001298af48c942d59ea /drivers/iio/imu/adis_trigger.c
parentb600bd7eb333554518b4dd36b882b2ae58a5149e (diff)
downloadlinux-stable-31fa357ac809affd9f9a7d0b5d1991951e16beec.tar.gz
linux-stable-31fa357ac809affd9f9a7d0b5d1991951e16beec.tar.bz2
linux-stable-31fa357ac809affd9f9a7d0b5d1991951e16beec.zip
iio: adis: handle devices that cannot unmask the drdy pin
Some devices can't mask/unmask the data ready pin and in those cases each driver was just calling '{dis}enable_irq()' to control the trigger state. This change, moves that handling into the library by introducing a new boolean in the data structure that tells the library that the device cannot unmask the pin. On top of controlling the trigger state, we can also use this flag to automatically request the IRQ with 'IRQF_NO_AUTOEN' in case it is set. So far, all users of the library want to start operation with IRQs/DRDY pin disabled so it should be fairly safe to do this inside the library. Signed-off-by: Nuno Sá <nuno.sa@analog.com> Link: https://lore.kernel.org/r/20210903141423.517028-3-nuno.sa@analog.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/imu/adis_trigger.c')
-rw-r--r--drivers/iio/imu/adis_trigger.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/iio/imu/adis_trigger.c b/drivers/iio/imu/adis_trigger.c
index 48eedc29b28a..c461bd1e8e69 100644
--- a/drivers/iio/imu/adis_trigger.c
+++ b/drivers/iio/imu/adis_trigger.c
@@ -30,6 +30,10 @@ static const struct iio_trigger_ops adis_trigger_ops = {
static int adis_validate_irq_flag(struct adis *adis)
{
unsigned long direction = adis->irq_flag & IRQF_TRIGGER_MASK;
+
+ /* We cannot mask the interrupt so ensure it's not enabled at request */
+ if (adis->data->unmasked_drdy)
+ adis->irq_flag |= IRQF_NO_AUTOEN;
/*
* Typically this devices have data ready either on the rising edge or
* on the falling edge of the data ready pin. This checks enforces that