linux-drivers/
drivers/input/touchscreen

Touchscreen controllers (mixed vendors and buses)

A broad collection of drivers for touchscreen controllers used in phones, tablets, kiosks, industrial panels, and single-board-computer displays. It covers chips from many vendors (Goodix, Atmel maXTouch, Novatek, Elan, Synaptics, Hynitron, and others) on I2C, SPI, and USB, from 1990s resistive panels to modern multi-touch capacitive parts.

keep conf=0.95 deploy=high replacement=none subsystem=input category=input-hid
95%

recommendation

It should stay because this is an actively maintained umbrella directory containing roughly a hundred drivers for touchscreen controllers from many vendors, spanning I2C, SPI, USB, and platform buses. New chips are still being added in 2025 (for example Hynitron CST816x), existing Goodix, Atmel, and Novatek drivers continue to receive fixes, and new touchscreen hardware such as the Raspberry Pi Touch Display 2 keeps shipping.

repository signals

120 files
62,392 source lines
518 commits, 5y
+14,175 / −9,196 lines added / removed, 5y
129 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 518 total · active in 56/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 11 commits · +196 −83 2021-06: 14 commits · +212 −200 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 18 commits · +757 −275 2021-10: 8 commits · +569 −29 2021-11: 4 commits · +48 −26 2021-12: 14 commits · +380 −26 2022-01: 6 commits · +33 −33 2022-02: 2 commits · +16 −3 2022-03: 9 commits · +477 −69 2022-04: 1 commit · +56 −56 2022-05: 3 commits · +18 −22 2022-06: 8 commits · +96 −19 2022-07: 3 commits · +16 −15 2022-08: 6 commits · +34 −50 2022-09: 12 commits · +117 −896 2022-10: 4 commits · +1,429 −477 2022-11: 57 commits · +698 −193 2022-12: 2 commits · +5 −3 2023-01: 50 commits · +221 −224 2023-02: 3 commits · +14 −3 2023-03: 8 commits · +44 −11 2023-04: 15 commits · +608 −301 2023-05: 12 commits · +2,862 −145 2023-06: 20 commits · +123 −253 2023-07: 26 commits · +219 −300 2023-08: 1 commit · +1 −0 2023-09: 9 commits · +18 −35 2023-10: 2 commits · +31 −7 2023-11: 1 commit · +3 −2 2023-12: 4 commits · +66 −72 2024-01: 3 commits · +1,066 −0 2024-02: 1 commit · +0 −1 2024-03: 6 commits · +105 −25 2024-04: 1 commit · +1 −1 2024-05: 9 commits · +125 −81 2024-06: 22 commits · +442 −248 2024-07: 21 commits · +698 −1,047 2024-08: 28 commits · +381 −3,374 2024-09: 3 commits · +16 −16 2024-10: 11 commits · +122 −83 2024-11: 1 commit · +1 −1 2024-12: 2 commits · +9 −8 2025-01: 6 commits · +23 −21 2025-02: 4 commits · +503 −3 2025-03: 2 commits · +79 −26 2025-04: 4 commits · +13 −15 2025-05: 2 commits · +8 −7 2025-06: 4 commits · +52 −12 2025-07: 2 commits · +9 −13 2025-08: 4 commits · +9 −7 2025-09: 8 commits · +883 −63 2025-10: 4 commits · +5 −30 2025-11: 1 commit · +4 −0 2025-12: 8 commits · +20 −18 2026-01: 18 commits · +91 −74 2026-02: 2 commits · +56 −56 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. cateee.net

    LKDDb shows INPUT_TOUCHSCREEN still covers many current IDs across ACPI/I2C/OF/platform bindings through 6.19/7.0, including recently added controllers and boards.

  2. git.kernel.org

    The directory is an actively maintained umbrella for a large set of touchscreen drivers across many vendors and buses, not a single legacy device driver.

  3. raspberrypi.com

    New touchscreen-equipped hardware was still on sale in the mid-2020s, demonstrating ongoing new deployments for this subsystem class.

codex reasoning notes (technical)

Local shell inspection of Makefile/Kconfig showed ~100+ concrete touchscreen drivers, and local git log for 2025-2026 showed recent substantive changes plus new-driver additions (for example Hynitron CST816x and current fixes for Goodix/Atmel/Novatek-class devices), with no sign of subsystem-wide removal. URL evidence: LKDDb page obtained via web search; git.kernel.org tree URL and Raspberry Pi product page used by canonical recall of stable pages. Because this path is a broad, still-active subsystem directory with contemporary hardware support, the correct outcome is keep, not deprecate/remove.