# # Industrial I/O standalone triggers # # When adding new entries keep the list in alphabetical order menu "Triggers - standalone" config [31mCONFIG_IIO_HRTIMER_TRIGGER[0m tristate "High resolution timer trigger" depends on [31mCONFIG_IIO_SW_TRIGGER[0m help Provides a frequency based [31mCONFIG_IIO[0m trigger using high resolution timers as interrupt source. To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be called iio-trig-hrtimer. config [31mCONFIG_IIO_INTERRUPT_TRIGGER[0m tristate "Generic interrupt trigger" help Provides support for using an interrupt of any type as an [31mCONFIG_IIO[0m trigger. This may be provided by a gpio driver for example. To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be called iio-trig-interrupt. config [31mCONFIG_IIO_TIGHTLOOP_TRIGGER[0m tristate "A kthread based hammering loop trigger" depends on [31mCONFIG_IIO_SW_TRIGGER[0m help An experimental trigger, used to allow sensors to be sampled as fast as possible under the limitations of whatever else is going on. Uses a tight loop in a kthread. Will only work with lower half only trigger consumers. To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be called iio-trig-loop. config [31mCONFIG_IIO_SYSFS_TRIGGER[0m tristate "SYSFS trigger" depends on [31mCONFIG_SYSFS[0m select [31mCONFIG_IRQ_WORK[0m help Provides support for using [31mCONFIG_SYSFS[0m entries as [31mCONFIG_IIO[0m triggers. If unsure, say N (but it's safe to say "Y"). To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be called iio-trig-sysfs. endmenu |