Mobiveil GPEX PCIe host controller (NXP Layerscape Gen4 and Xilinx/AMD Zynq UltraScale+)
Bridge logic that lets ARM-based system-on-chip designs talk to PCI Express devices, based on a soft IP block licensed from Mobiveil. It is used in NXP's Layerscape Gen4 networking processors (such as the LX2160A) and in AMD/Xilinx Zynq UltraScale+ MPSoC FPGA platforms commonly found in embedded, industrial, and communications gear from the late 2010s onward.
recommendation
It should stay in the kernel because it is the host-side PCIe controller code for SoCs that are still actively sold and deployed, including NXP's Layerscape LX2160A networking processors and AMD/Xilinx Zynq UltraScale+ MPSoCs (which AMD commits to supplying through 2045). The code was still receiving upstream cleanup attention in 2026 and has no generic replacement, so removing it would break working embedded and networking hardware.
repository signals
sources
- lore.kernel.org
`pcie-mobiveil.c` was still being touched by upstream PCI core cleanup work in April 2026, indicating the code is live and maintained rather than abandoned.
- nxp.com
NXP lists the LX2160A Layerscape processor as Active; the in-tree `pcie-layerscape-gen4.c` driver variant targets `fsl,lx2160a-pcie`.
- amd.com
AMD states Zynq UltraScale+ MPSoCs have lifespans extending through 2045; the Mobiveil menu/Kconfig includes the platform variant for `ARCH_ZYNQMP`, supporting ongoing new deployments in embedded designs.
codex reasoning notes (technical)
Real driver directory: local `exec_command` inspection showed Kconfig entries for `PCIE_LAYERSCAPE_GEN4` and `PCIE_MOBIVEIL_PLAT`, plus platform-driver code and DT compatibles (`mbvl,gpex40-pcie`, `fsl,lx2160a-pcie`). `lore_file_timeline` on `drivers/pci/controller/mobiveil/pcie-mobiveil.c` showed active upstream traffic in 2026 and no sign of removal in sampled activity. NXP and AMD URLs were obtained via `web.search_query`; they show relevant supported silicon families still marketed for new designs. This is SoC/soft-IP PCIe host-controller code with no obvious generic replacement driver; deprecation would strand active embedded/networking platforms.