Qualcomm Adreno GPUs (MSM DRM driver)
Qualcomm's Adreno is the integrated GPU found in Snapdragon mobile and PC chips, powering display rendering and 3D acceleration on Android phones, tablets, Chromebooks, and the Snapdragon X Elite laptops. The kernel side of the MSM DRM stack handles GPU command submission, memory management, and power control for Adreno generations spanning roughly the A2xx series up through current A7xx parts.
recommendation
It should stay in the kernel because Adreno is the GPU inside virtually every Snapdragon-powered phone, tablet, and the new Snapdragon X Elite Windows-on-Arm and Linux laptops shipping from 2024 onward. The driver is under heavy active development, with hundreds of commits in recent years from dozens of contributors and ongoing enablement for new Adreno generations.
repository signals
sources
- linux.googlesource.com
The MSM Adreno DRM driver is listed as Maintained, covering drivers/gpu/drm/msm/.
- lkml.rescloud.iu.edu
A 2024 patch series added Adreno 505 GPU support, showing ongoing upstream enablement rather than retirement.
- cateee.net
CONFIG_DRM_MSM remains present through 7.0-rc+HEAD, with Adreno-related platform/OF matches and recent Qualcomm SoC bindings in the MSM DRM stack.
- qualcomm.com
Qualcomm's current Snapdragon mobile platforms continue to ship with Adreno GPUs, indicating the hardware family is still sold new in 2025.
- qualcomm.com
Snapdragon X Elite announced Adreno-equipped PC platforms shipping from mid-2024, extending current Adreno deployments beyond phones.
codex reasoning notes (technical)
Recommendation is keep: the prompt's local history stats already show very high recent activity (449 substantive commits in 5y, latest 2026-03-05, 60 authors), and cited evidence matches that this is an actively maintained upstream driver with new GPU enablement and current-product relevance. No removal/deprecation signal surfaced in available search results; lore-http was unavailable in-session and `lei` was missing, so that specific point is inferred from the supplied activity metadata plus web evidence rather than direct lore timeline output. URLs were obtained via web search results: MAINTAINERS and LKDDb from search, LKML archive patch page from search, and Qualcomm product/release pages from search.