It really doesn't matter if the poll is triggered from a fastpath or threaded IRQ, the IIO core runs its own interrupt thread anyway. Sometimes this is connected to a hard IRQ line, sometimes to something on an I2C expander that needs to run from a thread, so request any context IRQ. Cc: Denis Ciocca <denis.ciocca@xxxxxx> Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> --- drivers/iio/common/st_sensors/st_sensors_trigger.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/iio/common/st_sensors/st_sensors_trigger.c b/drivers/iio/common/st_sensors/st_sensors_trigger.c index 3c0aa17d753f..e33796cdd607 100644 --- a/drivers/iio/common/st_sensors/st_sensors_trigger.c +++ b/drivers/iio/common/st_sensors/st_sensors_trigger.c @@ -32,9 +32,8 @@ int st_sensors_allocate_trigger(struct iio_dev *indio_dev, goto iio_trigger_alloc_error; } - err = request_threaded_irq(sdata->get_irq_data_ready(indio_dev), + err = request_any_context_irq(sdata->get_irq_data_ready(indio_dev), iio_trigger_generic_data_rdy_poll, - NULL, IRQF_TRIGGER_RISING, sdata->trig->name, sdata->trig); -- 2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
