Linux LED triggers
A collection of small modules that connect status LEDs on a system to events the kernel already knows about, such as disk activity, network traffic, CPU load, heartbeat, keyboard input, or user-space-defined patterns. They are what makes the activity lights on laptops, servers, and embedded devices like Wi-Fi routers blink in meaningful ways.
recommendation
It should stay because LED triggers are core, generic Linux infrastructure that drives the activity blinkenlights on shipping hardware, from laptops to routers. The subsystem is still actively maintained, with 2025 patches adding new triggers (such as a userspace-controlled trigger) and ongoing fixes, and projects like OpenWrt rely on it for power, Ethernet, USB, and Wi-Fi status LEDs on current devices.
repository signals
sources
- lore.kernel.org
Recent upstream maintenance in 2025 touched this subtree's Kconfig, indicating the trigger family is still actively maintained.
- lore.kernel.org
A 2025 patch series added a new userspace LED trigger, showing the subsystem is still gaining new functionality rather than being phased out.
- docs.kernel.org
Kernel documentation describes LED triggers as a kernel-based source of LED events available to LED class devices, confirming this is generic current kernel functionality rather than a legacy single-device driver.
- openwrt.org
OpenWrt documents LED trigger configuration for power, ethernet, USB, and Wi-Fi indicators on contemporary routers, evidencing ongoing real-world deployments on new embedded hardware.
codex reasoning notes (technical)
`drivers/leds/trigger` contains loadable LED trigger modules (`ledtrig-netdev`, `ledtrig-pattern`, `ledtrig-input-events`, etc.), so it is a real driver-family directory, not a helper library. `lore_file_timeline` on `drivers/leds/trigger/Kconfig` showed steady 2021-2025 activity and produced the cited lore URLs; notable events include a 2025 Kconfig fix and a 2025 new userspace-trigger series, with no removal/deprecation signal visible in that timeline. `web.search_query` returned the kernel LED docs URL and the OpenWrt LED configuration URL; together they show these triggers remain part of current Linux LED infrastructure and are used on shipping embedded/network devices. Because this is generic subsystem functionality with ongoing additions and broad deployment, there is no natural replacement driver and the correct recommendation is to keep it.