blob: 809b2e7d58faf5435f6ca1d70f5c183f5d526eb2 [file] [log] [blame]
Jonathan Camerone64e7d52013-04-14 12:54:00 +01001#
2# Industrial I/O standalone triggers
3#
Lars-Peter Clausen3edc84e2013-07-15 08:45:00 +01004# When adding new entries keep the list in alphabetical order
5
Jonathan Camerone64e7d52013-04-14 12:54:00 +01006menu "Triggers - standalone"
7
Daniel Balutaac5006a2015-11-09 09:14:01 +02008config 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
Jonathan Cameronc7a8be02013-06-02 20:00:00 +010018config 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
Jonathan Cameronbc2e1122016-03-06 20:02:56 +000027config IIO_TIGHTLOOP_TRIGGER
28 tristate "A kthread based hammering loop trigger"
29 depends on IIO_SW_TRIGGER
30 help
31 An experimental trigger, used to allow sensors to be sampled as fast
32 as possible under the limitations of whatever else is going on.
33 Uses a tight loop in a kthread. Will only work with lower half only
34 trigger consumers.
35
36 To compile this driver as a module, choose M here: the
37 module will be called iio-trig-loop.
38
Jonathan Camerone64e7d52013-04-14 12:54:00 +010039config IIO_SYSFS_TRIGGER
40 tristate "SYSFS trigger"
41 depends on SYSFS
42 select IRQ_WORK
43 help
Peter Meerwald93232cd2013-06-23 22:28:00 +010044 Provides support for using SYSFS entries as IIO triggers.
Jonathan Camerone64e7d52013-04-14 12:54:00 +010045 If unsure, say N (but it's safe to say "Y").
46
47 To compile this driver as a module, choose M here: the
48 module will be called iio-trig-sysfs.
49
50endmenu