drivers/leds/flash

Camera flash and torch LED controllers

A collection of small chips from Qualcomm, Texas Instruments, MediaTek, Richtek and others that drive the high-brightness LEDs used as camera flashes and flashlights ("torch" mode) on phones, tablets, and embedded devices. They handle current regulation and timing so the kernel's LED and V4L2 camera layers can fire the flash in sync with image capture.

keep conf=0.84 last_sold=2025 deploy=medium replacement=none subsystem=leds category=other
84%

recommendation

It should stay in the kernel because this is a live subsystem covering hardware still shipping in 2025, including TI's LM36011 (listed as active and orderable) and Qualcomm PMIC flash blocks that received bugfixes and stable-tagged patches on linux-leds in 2024 and 2025. The flash LED class is documented as a current API and is actively used by camera pipelines, so there is no sign of deprecation.

repository signals

15 files
8,172 source lines
67 commits, 5y
+7,777 / −301 lines added / removed, 5y
35 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 67 total · active in 28/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 7 commits · +3,667 −1 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 1 commit · +924 −0 2021-12: 1 commit · +1 −1 2022-01: 0 commits · +0 −0 2022-02: 1 commit · +1 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 2 commits · +6 −11 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 3 commits · +11 −13 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 1 commit · +6 −32 2023-02: 0 commits · +0 −0 2023-03: 3 commits · +1,378 −2 2023-04: 0 commits · +0 −0 2023-05: 6 commits · +19 −10 2023-06: 1 commit · +1 −0 2023-07: 3 commits · +7 −0 2023-08: 0 commits · +0 −0 2023-09: 4 commits · +17 −29 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 2 commits · +30 −92 2024-02: 3 commits · +5 −2 2024-03: 0 commits · +0 −0 2024-04: 2 commits · +11 −3 2024-05: 2 commits · +3 −2 2024-06: 2 commits · +555 −1 2024-07: 3 commits · +181 −7 2024-08: 6 commits · +30 −31 2024-09: 3 commits · +5 −13 2024-10: 1 commit · +7 −7 2024-11: 1 commit · +1 −0 2024-12: 1 commit · +1 −1 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 1 commit · +5 −5 2025-05: 3 commits · +840 −6 2025-06: 1 commit · +1 −0 2025-07: 2 commits · +60 −27 2025-08: 0 commits · +0 −0 2025-09: 1 commit · +4 −5 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    linux-leds carried a 2025 fix series for `leds-qcom-flash`, showing active upstream maintenance rather than abandonment.

  2. lore.kernel.org

    `leds-qcom-flash` received a 2025 bugfix tagged for stable, indicating current deployed users and ongoing support expectations.

  3. docs.kernel.org

    The kernel documents LED flash handling as an active class API for torch/flash devices and V4L2 integration, confirming this is a live subsystem use case.

  4. ti.com

    Texas Instruments lists LM36011, a Linux-supported flash LED controller family member (`leds-lm3601x`), as ACTIVE and orderable in 2025.

codex reasoning notes (technical)

Local shell inspection showed this directory is a bundle of vendor-specific flash/torch LED controller drivers (Qualcomm, TI, MediaTek, Richtek, etc.), not a dead singleton. `lore_activity` on `drivers/leds/flash/leds-qcom-flash.c` returned multiple 2024-2025 fixes/features with stable CC on one patch; no removal/deprecation evidence surfaced from the lore checks attempted. Web search found current kernel flash-LED class docs and TI's ACTIVE LM36011 product page, supporting ongoing real hardware availability. URLs were obtained via `lore_activity` and `web.search_query`; directory composition came from local shell (`rg --files`, `sed` on Kconfig).