xref: /openbmc/linux/drivers/iio/trigger/Kconfig (revision 4f6cce39)
1#
2# Industrial I/O standalone triggers
3#
4# When adding new entries keep the list in alphabetical order
5
6menu "Triggers - standalone"
7
8config IIO_HRTIMER_TRIGGER
9	tristate "High resolution timer trigger"
10	depends on IIO_SW_TRIGGER
11	help
12	  Provides a frequency based IIO trigger using high resolution
13	  timers as interrupt source.
14
15	  To compile this driver as a module, choose M here: the
16	  module will be called iio-trig-hrtimer.
17
18config IIO_INTERRUPT_TRIGGER
19	tristate "Generic interrupt trigger"
20	help
21	  Provides support for using an interrupt of any type as an IIO
22	  trigger.  This may be provided by a gpio driver for example.
23
24	  To compile this driver as a module, choose M here: the
25	  module will be called iio-trig-interrupt.
26
27config IIO_STM32_TIMER_TRIGGER
28	tristate "STM32 Timer Trigger"
29	depends on (ARCH_STM32 && OF && MFD_STM32_TIMERS) || COMPILE_TEST
30	help
31	  Select this option to enable STM32 Timer Trigger
32
33	  To compile this driver as a module, choose M here: the
34	  module will be called stm32-timer-trigger.
35
36config IIO_TIGHTLOOP_TRIGGER
37	tristate "A kthread based hammering loop trigger"
38	depends on IIO_SW_TRIGGER
39	help
40	  An experimental trigger, used to allow sensors to be sampled as fast
41	  as possible under the limitations of whatever else is going on.
42	  Uses a tight loop in a kthread.  Will only work with lower half only
43	  trigger consumers.
44
45	  To compile this driver as a module, choose M here: the
46	  module will be called iio-trig-loop.
47
48config IIO_SYSFS_TRIGGER
49	tristate "SYSFS trigger"
50	depends on SYSFS
51	select IRQ_WORK
52	help
53	  Provides support for using SYSFS entries as IIO triggers.
54	  If unsure, say N (but it's safe to say "Y").
55
56	  To compile this driver as a module, choose M here: the
57	  module will be called iio-trig-sysfs.
58
59endmenu
60