drivers/phy/lantiq

Lantiq XWAY, VRX200, and ARX300 SoC PHY controllers

On-chip PHY (physical-layer) blocks built into Lantiq's XWAY, VRX200, and ARX300 system-on-chip families, which powered DSL home gateways and broadband customer-premises equipment from the late 2000s and 2010s. The PCIe PHY in particular is what lets those SoCs talk to add-on chips like Wi-Fi cards in routers still running OpenWrt today.

deprecate conf=0.76 deploy=low replacement=none subsystem=phy category=bus-other
76%

recommendation

A candidate for future removal because the Lantiq brand is long defunct — the line passed from Lantiq to Intel in 2015 and then to MaxLinear in 2020 — and the directory has seen only one substantive commit in the last five years (most recent in February 2024). It still has real users, since OpenWrt continues to ship current images for the lantiq/xrx200 target, so removal is not urgent, but no new silicon is being designed around these PHYs and upstream activity is limited to treewide cleanup churn.

repository signals

4 files
748 source lines
2 commits, 5y
+1 / −2 lines added / removed, 5y
2 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 2 total · active in 2/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 1 commit · +0 −1 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 1 commit · +1 −1 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Recent upstream touches are treewide PHY header churn, not evidence of active feature work for this Lantiq PHY directory.

  2. downloads.openwrt.org

    OpenWrt still publishes current images for the `lantiq/xrx200` target, indicating a surviving installed base in legacy CPE/router deployments.

  3. cateee.net

    The in-tree scope is narrow: this directory serves Lantiq VRX200/ARX300 PCIe PHY support in current kernels.

  4. en.wikipedia.org

    Lantiq is a defunct vendor brand; the product line changed hands to Intel in 2015 and MaxLinear in 2020, consistent with these SoCs being legacy rather than current-design silicon.

codex reasoning notes (technical)

Local shell read of Kconfig/C files shows two SoC-internal PHY drivers only, for XWAY/VRX200/ARX300 families, with no obvious generic replacement. lore_file_timeline/lore_activity showed mostly historical traffic plus a 2026 treewide include cleanup; the user-provided static summary says just 1 substantive commit in 5y, latest 2024-02-23, which fits low-maintenance legacy status. Web search produced the OpenWrt current xrx200 target URL and LKDDb page; those support low but nonzero deployment today. Wikipedia URL came from web search and is used only for vendor-lineage context; 'not sold new in 2025' is an inference from legacy SoC family age, defunct branding, and lack of modern platform evidence, so I leave last_widely_available_year as null rather than fabricate an exact cutoff.