VFIO Passthrough for NXP QorIQ/Layerscape DPAA2 Devices
Provides device passthrough into virtual machines and userspace for NXP's QorIQ and Layerscape DPAA2 system-on-chip platforms, which use a vendor-specific Management Complex bus instead of PCI to expose networking accelerators, crypto engines, and other on-chip objects. It is mostly used in carrier-grade networking and edge appliances built on parts like the LX2160A.
recommendation
Worth keeping but documenting its niche. Upstream marked it for removal in August 2025 after it sat orphaned for more than a year, but in February 2026 NXP stepped in as maintainer and confirmed the driver is still actively used on Layerscape DPAA2 hardware. Since NXP continues to ship LX2160A and related Layerscape parts as current products for networking and edge applications, the passthrough support remains relevant; it just deserves a note in the tree about its near-removal and the reaffirmed maintenance status.
repository signals
sources
- lore.kernel.org
Upstream marked vfio/fsl-mc for removal in August 2025 because it had been orphaned for over a year.
- lore.kernel.org
In February 2026 NXP took maintainership and stated the driver is still highly in use on Layerscape DPAA2 SoCs.
- nxp.com
NXP still lists the LX2160A Layerscape processor as Active and describes DPAA2-based networking/edge use cases, indicating the hardware family remains sold for new deployments.
codex reasoning notes (technical)
Real driver directory: Kconfig names 'VFIO support for QorIQ DPAA2 fsl-mc bus devices' and local source uses module_fsl_mc_driver. Removal evidence came from local git commit inspection via exec_command, which exposed the lore URL for the 2025 'Mark for removal' patch. Counter-evidence also came from local git commit inspection via exec_command, which exposed the lore URL for the 2026 maintainer addition stating the driver is still highly in use. Hardware-market evidence came from web search on NXP's official LX2160A page. Net: niche but current DPAA2 passthrough support with active upstream attention after a removal scare, so keep it but annotate the prior removal discussion.