drivers/iio/trigger · keep

IIO trigger providers (software timers and STM32 TIM/LPTIM)

A small collection of trigger sources used by the Linux Industrial I/O subsystem to tell sensors and ADCs when to take a reading. It includes generic software triggers driven by kernel timers, interrupts, sysfs writes, or busy loops, plus drivers that turn the general-purpose and low-power timer blocks on STMicroelectronics STM32 microcontrollers and MPUs into hardware sampling triggers.

keep conf=0.82 deploy=medium replacement=none subsystem=iio category=sensor-iio

82%

recommendation

It should stay because these are the trigger sources that the wider Industrial I/O sensor framework depends on to schedule sample captures, including generic software triggers (high-resolution timer, interrupt, sysfs, tight loop) and the timer blocks on STMicroelectronics STM32 SoCs. The code is actively maintained, has no replacement, and STM32MP1-class chips that need the hardware triggers are still being sold and designed into industrial and IoT products in 2025.

repository signals

8 files

1,770 source lines

28 commits, 5y

+183 / −127 lines added / removed, 5y

23 authors, 5y

monthly commits · 2021-04-21 → 2026-04-21 · 28 total · active in 22/61 months

sources

docs.kernel.org
Kernel documentation describes IIO triggers as a current subsystem mechanism, including timer, interrupt, and sysfs-provided triggers used by multiple sensors/drivers.
st.com
Current STM32MP153C product page lists multiple general-purpose timers and low-power timers, matching the STM32 TIM/LPTIM trigger use case.
st.com
STM32MP1 series is an actively marketed embedded platform in current industrial/IoT/medical/automation deployments, supporting ongoing relevance for STM32 timer-trigger integration.

codex reasoning notes (technical)

Real driver directory: six .c files with module entry points, including generic software triggers and STM32 platform drivers. Local Kconfig inspection via shell showed active configs for hrtimer, interrupt, sysfs, tightloop, STM32 timer, and STM32 low-power timer triggers. lore_file_timeline(path='drivers/iio/trigger') returned no events, which appears to reflect directory-path indexing limits rather than inactivity; prompt metadata already shows 25 substantive commits in 5y with last substantive touch on 2025-06-26 and 19 authors, so this is not a dead driver set. Local git subject grep over the path found no obvious remove/deprecate/obsolete commits. URLs were obtained via web search (`docs.kernel.org`, `st.com`). No natural replacement exists because these are the trigger providers themselves rather than a superseded hardware family.