Renesas RZ/G2L and RZ/V2H Display Unit
Provides display output for Renesas RZ/G2L and RZ/V2H system-on-chip processors, which are 64-bit Arm SoCs aimed at industrial human-machine interfaces, embedded vision, and AI edge devices. The hardware drives panels and MIPI-DSI displays on boards built around chips like the r9a07g044, r9a07g043u, and r9a09g057, all introduced in the 2020s and still being shipped new.
recommendation
It should stay because this is a young, actively maintained driver for current Renesas embedded SoCs that the vendor is still selling new and has committed to supplying through 2037. Deployments are niche, mostly industrial HMIs, vision/AI gateways, and similar embedded designs rather than consumer hardware, but upstream work continues, including recently added support for the newer RZ/V2H(P) chip.
repository signals
sources
- git.kernel.org
Upstream activity is current rather than sunset; local git log on this directory shows regular fixes/features through 2026-03-02, including reboot fixes and added RZ/V2H(P) support, with no visible removal trend.
- cateee.net
LKDDb shows CONFIG_DRM_RZG2L_DU present in mainline kernels 6.9 through 6.19 and 7.0-rc+HEAD, with supported compatibles r9a07g044, r9a07g043u, and r9a09g057.
- renesas.com
Renesas lists RZ/G2L as Active, with product longevity to 2037, and describes display interfaces plus Linux support for industrial HMI/embedded designs.
- renesas.com
Renesas lists RZ/V2H as Active and exposes MIPI-DSI/display-capable Linux-oriented AI MPU positioning, matching the newer SoC support added in this driver.
codex reasoning notes (technical)
Real driver directory: DRM/KMS code with module/device tables for Renesas DU hardware. Evidence chain: local source inspection via shell `rg` identified RZ/G2L/RZ/V2H compatibles and module descriptions; local shell `git log` showed active substantive work and no removal discussion in visible history; web search returned official Renesas product pages and LKDDb. Kernel.org log URL is canonical recall, paired with the local git-log result because lore/lei was unavailable in this environment. Recommendation stays `keep`: the driver is only ~2 years old, actively maintained, and targets still-active embedded SoCs for ongoing industrial/vision deployments. Deployments are likely niche rather than mass-market, so `low` rather than `medium`.