iio: trigger: drop generic interrupt trigger.
Jonathan Cameron
maintainerPATCH 1/1 iio: trigger: drop generic interrupt trigger.
There is no way to bind to this driver from firmware and no explicit platform device creation calls exist in mainline.
As such it is dead code. So drop it rather than potentially wasting time modernizing it (see #1)
---
Long ago this was somewhat useful, but seems no one cares any more! If anyone has a usecase then shout - if not it will be easy to bring back anyway if one surfaces. At that point we can modernize it.
drivers/iio/trigger/Kconfig | 9 -- drivers/iio/trigger/Makefile | 1 - drivers/iio/trigger/iio-trig-interrupt.c | 109 ----------------------- 3 files changed, 119 deletions(-) delete mode 100644 drivers/iio/trigger/iio-trig-interrupt.c
drivers/iio/trigger/Kconfig +0 -9
@@ -16,15 +16,6 @@ config IIO_HRTIMER_TRIGGER To compile this driver as a module, choose M here: the module will be called iio-trig-hrtimer. -config IIO_INTERRUPT_TRIGGER - tristate "Generic interrupt trigger" - help - Provides support for using an interrupt of any type as an IIO - trigger. This may be provided by a gpio driver for example. - - To compile this driver as a module, choose M here: the - module will be called iio-trig-interrupt. - config IIO_STM32_LPTIMER_TRIGGER tristate "STM32 Low-Power Timer Trigger" depends on MFD_STM32_LPTIMER || COMPILE_TEST
drivers/iio/trigger/Makefile +0 -1
@@ -6,7 +6,6 @@ # When adding new entries keep the list in alphabetical order obj-$(CONFIG_IIO_HRTIMER_TRIGGER) += iio-trig-hrtimer.o -obj-$(CONFIG_IIO_INTERRUPT_TRIGGER) += iio-trig-interrupt.o obj-$(CONFIG_IIO_STM32_LPTIMER_TRIGGER) += stm32-lptimer-trigger.o obj-$(CONFIG_IIO_STM32_TIMER_TRIGGER) += stm32-timer-trigger.o obj-$(CONFIG_IIO_SYSFS_TRIGGER) += iio-trig-sysfs.o
drivers/iio/trigger/iio-trig-interrupt.c deleted +0 -109
109 lines not on this page · raw message
Signature · 1 line
2.54.0
Quoted 5 lines · Jonathan Cameron
There is no way to bind to this driver from firmware and no explicit platform device creation calls exist in mainline.
As such it is dead code. So drop it rather than potentially wasting time modernizing it (see #1)
Signature · 2 lines
With Best Regards, Andy Shevchenko
Quoted 9 lines · On Mon, 18 May 2026 10:58:54 +0300 Andy Shevchenko…
Quoted 5 lines · Jonathan Cameron
There is no way to bind to this driver from firmware and no explicit platform device creation calls exist in mainline.
As such it is dead code. So drop it rather than potentially wasting time modernizing it (see #1)
Reviewed-by Andy Shevchenko <[email protected]>
Applied. I'm fine reverting this if a user shouts - until then let us assume that no one cares (any more!)
Jonathan