drivers/phy/ingenic

Ingenic JZ and X-series SoC USB PHY

The USB physical-layer interface block built into Ingenic's JZ-series (JZ4770, JZ4775, JZ4780) and X-series (X1000, X1830, X2000) MIPS/XBurst SoCs, which Ingenic ships for embedded and industrial gadgets such as cameras, smart speakers, and small Linux appliances. It sits between the SoC's USB controller and the actual USB port, handling signaling and power-up.

keep-annotate conf=0.79 deploy=low replacement=none subsystem=phy category=bus-other
79%

recommendation

Worth keeping but documenting as a niche, low-activity component. Ingenic still sells X1000 and X2000 chips for embedded and industrial use, and there is no generic replacement for this SoC-specific USB PHY block, so removing it would break those boards. Upstream activity is sparse (mostly tree-wide cleanups rather than feature work), which fits a quiet but still-needed driver rather than one heading for removal.

repository signals

3 files
386 source lines
2 commits, 5y
+3 / −6 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 · +1 −0 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: 0 commits · +0 −0 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: 1 commit · +2 −6 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. git.kernel.org

    Kernel Kconfig describes this as the USB PHY driver for Ingenic JZ-series and X-series SoCs.

  2. lore.kernel.org

    Recent lore-visible touch affecting this file was a broad cross-tree PHY header include change, indicating low but nonzero upstream maintenance rather than active feature work.

  3. en.ingenic.com.cn

    Ingenic's live product catalog still lists X1000 and X2000 in the X Series, showing the family remains commercially present.

  4. en.ingenic.com.cn

    Ingenic still publishes a current X2000 product page, supporting that at least part of the supported SoC family is still sold for embedded use.

codex reasoning notes (technical)

Local tree inspection with `rg` shows a real platform USB PHY driver with OF matches for jz4770/jz4775/jz4780/x1000/x1830/x2000. The kernel.org Kconfig URL is a canonical recall URL used to back that scope claim. `lore_file_timeline` on `drivers/phy/ingenic/phy-ingenic-usb.c` showed only sparse recent activity and surfaced a 2026 treewide include clean-up patch via the cited lore URL; within the allotted budget I found no concrete removal-series evidence, so this looks dormant/niche rather than removal-bound. `web.search_query` found Ingenic's live product catalog and X2000 page, so hardware is still sold new, but likely only in niche embedded/industrial deployments. There is no natural generic replacement for this SoC-specific PHY block, so the pragmatic outcome is keep the driver but annotate it as low-activity niche support.