NXP/Freescale DPAA2 Layerscape Ethernet and L2 Switch
The networking block (DPAA2 / WRIOP) built into NXP Layerscape and QorIQ ARM-based SoCs, such as the LX2160A, providing on-chip multi-gigabit Ethernet interfaces, an integrated Layer 2 switch, and IEEE 1588 PTP timestamping. These chips are used in routers, 5G infrastructure, industrial gateways, and storage/networking appliances from the late 2010s through today.
recommendation
It should stay because the underlying hardware — NXP's Layerscape/QorIQ SoCs such as the LX2160A — is still actively sold in 2025 for networking and edge appliances, and the code is receiving fresh feature work and fixes well into 2026 (including hardware timestamping additions and switch-side bugfixes). No removal or deprecation effort is in flight.
repository signals
sources
- git.kernel.org
Recent upstream fix in February 2026 for dpaa2-switch shows current maintenance activity.
- git.kernel.org
Recent functional work added ndo_hwtstamp_get() support to dpaa2-eth, indicating ongoing feature-level upkeep rather than abandonment.
- cateee.net
CONFIG_FSL_DPAA2_ETH remains present through 7.0-rc+HEAD, showing the Ethernet driver is still upstream and buildable.
- cateee.net
CONFIG_FSL_DPAA2_SWITCH remains present through 7.0-rc+HEAD, showing the switch portion of this directory is also still upstream.
- nxp.com
NXP lists the LX2160A as Active and advertises DPAA2/WRIOP Ethernet and L2 switching capabilities, indicating hardware family is still sold for new deployments.
codex reasoning notes (technical)
Local shell inspection showed this is a real fsl-mc network driver directory with Kconfig entries for DPAA2 Ethernet, PTP, and switch, plus heavy recent git activity in 2024-2026; a local git grep for removal/deprecate/obsolete/orphan did not surface any actual deprecation series for the directory. Kernel commit URLs were formed by canonical recall from commit hashes obtained via local `git log`. LKDDb and NXP URLs were obtained via web search. The hardware is still an active but niche embedded/networking SoC family, so recommendation is keep, with medium current deployment rather than mass-market ubiquity.