Marvell MMP2 and PXA910 framebuffer display subsystem
Display controller and panel support for Marvell's MMP2 and PXA910 mobile application processors, which powered phones, tablets, and embedded boards around 2010 (the Armada 610 generation). It exposes the screen through the older framebuffer interface rather than the modern DRM graphics stack.
recommendation
A candidate for future removal because it serves a narrow set of Marvell mobile chips from around 2010 that are no longer sold, uses the legacy framebuffer interface that the kernel is steadily moving away from, and has seen only treewide cleanups (last substantive change in April 2022) rather than active development. There is no in-tree DRM replacement and no removal patches are currently on the lists, so the code still builds and works for anyone with surviving hardware, but its long-term prospects are poor.
repository signals
sources
- cateee.net
CONFIG_MMP_DISP is the Marvell MMP Display Subsystem driver, still present in current kernels, with modules/platform entries for mmp_disp and mmp-fb.
- cateee.net
The controller support is explicitly for Marvell PXA910 and MMP2 chips.
- marvell.com
ARMADA 610, the MMP2-era Marvell mobile SoC family, was launched on January 5, 2010 for phones/tablets/mobile devices.
codex reasoning notes (technical)
Real driver, not an early-exit case: local files show Kconfig/Makefile plus hw/, fb/, and panel/ code for a Marvell display stack. `exec_command` on local Kconfig identified PXA910/MMP2 scope and no DRM-side replacement in-tree; another `exec_command` using `git -c safe.directory=... log -- drivers/video/fbdev/mmp` showed mostly treewide cleanups since 2019 and no clear removal series. `web.search_query` for lore.kernel.org on the exact path/subject returned no hits, so I found no active upstream removal discussion; static metadata says last substantive touch was 2022-04-12, which supports low maintenance rather than active development. Deployment looks low: this is a fbdev driver for 2010-era Marvell mobile SoCs, likely only legacy embedded/industrial boards, with no evidence of new 2025 products. Chosen `deprecate` rather than `remove` because the code still builds in mainline and there is no demonstrated removal campaign or upstream replacement driver.