93fbe91b55
Timers IPs can be used to generate triggers for other IPs like DAC or ADC. Each trigger may result of timer internals signals like counter enable, reset or edge, this configuration could be done through "master_mode" device attribute. Since triggers could be used by DAC or ADC their names are defined in include/ nux/iio/timer/stm32-timer-trigger.h and is_stm32_iio_timer_trigger function could be used to check if the trigger is valid or not. "trgo" trigger have a "sampling_frequency" attribute which allow to configure timer sampling frequency. version 8: - change kernel version from 4.10 to 4.11 in ABI documentation version 7: - remove all iio_device related code - move driver into trigger directory version 5: - simplify tables of triggers - only create an IIO device when needed version 4: - get triggers configuration from "reg" in DT - add tables of triggers - sampling frequency is enable/disable when writing in trigger sampling_frequency attribute - no more use of interruptions version 3: - change compatible to "st,stm32-timer-trigger" - fix attributes access right - use string instead of int for master_mode and slave_mode - document device attributes in sysfs-bus-iio-timer-stm32 version 2: - keep only one compatible - use st,input-triggers-names and st,output-triggers-names to know which triggers are accepted and/or create by the device Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com> Acked-by: Jonathan Cameron <jic23@kernel.org> Signed-off-by: Lee Jones <lee.jones@linaro.org>
60 lines
1.7 KiB
Plaintext
60 lines
1.7 KiB
Plaintext
#
|
|
# Industrial I/O standalone triggers
|
|
#
|
|
# When adding new entries keep the list in alphabetical order
|
|
|
|
menu "Triggers - standalone"
|
|
|
|
config IIO_HRTIMER_TRIGGER
|
|
tristate "High resolution timer trigger"
|
|
depends on IIO_SW_TRIGGER
|
|
help
|
|
Provides a frequency based IIO trigger using high resolution
|
|
timers as interrupt source.
|
|
|
|
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_TIMER_TRIGGER
|
|
tristate "STM32 Timer Trigger"
|
|
depends on (ARCH_STM32 && OF && MFD_STM32_TIMERS) || COMPILE_TEST
|
|
help
|
|
Select this option to enable STM32 Timer Trigger
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called stm32-timer-trigger.
|
|
|
|
config IIO_TIGHTLOOP_TRIGGER
|
|
tristate "A kthread based hammering loop trigger"
|
|
depends on IIO_SW_TRIGGER
|
|
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 M here: the
|
|
module will be called iio-trig-loop.
|
|
|
|
config IIO_SYSFS_TRIGGER
|
|
tristate "SYSFS trigger"
|
|
depends on SYSFS
|
|
select IRQ_WORK
|
|
help
|
|
Provides support for using SYSFS entries as IIO triggers.
|
|
If unsure, say N (but it's safe to say "Y").
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called iio-trig-sysfs.
|
|
|
|
endmenu
|