drivers/phy/spacemit

SpacemiT K1 USB 2.0 PHY

Hardware support for the USB 2.0 PHY block built into SpacemiT's K1 RISC-V system-on-chip, which exposes three USB ports. The K1 powers recent RISC-V single-board computers such as the Sipeed LicheePi 3A that began shipping in the mid-2020s.

keep conf=0.93 deploy=low replacement=none subsystem=phy category=bus-usb
93%

recommendation

It should stay in the kernel because it is a brand-new driver for the USB 2.0 physical-layer block inside the SpacemiT K1 RISC-V SoC, freshly merged upstream and already receiving follow-up bug fixes. The K1 ships in current single-board computers like Sipeed's LicheePi 3A, and no generic replacement exists for this SoC-specific PHY hardware.

repository signals

3 files
214 source lines
2 commits, 5y
+229 / −0 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: 0 commits · +0 −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: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 1 commit · +215 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 1 commit · +14 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. spinics.net

    Initial upstream patch series for the SpacemiT K1 USB2 PHY says K1 has three USB ports and introduces this PHY driver.

  2. spinics.net

    Vinod Koul applied the v6 series on 2026-01-01, showing the driver was newly merged upstream rather than being abandoned.

  3. spinics.net

    A February 2026 bug-fix patch adds disconnect support for the K1 USB2 PHY, indicating active post-merge maintenance.

  4. spinics.net

    A March 2026 patch fixes an error path in spacemit_usb2phy_init(), further indicating ongoing maintenance and no removal trajectory.

  5. wiki.sipeed.com

    The LicheePi 3A board uses the Spacemit K1 SoC and exposes USB ports, showing real hardware deployment on current SBCs.

  6. wiki.sipeed.com

    Current image/install documentation lists multiple OS images for LicheePi 3A, suggesting the K1 platform remains in active use.

codex reasoning notes (technical)

Local evidence came from exec_command reading drivers/phy/spacemit/* and git log, which showed a single SoC-specific USB2 PHY driver with only two commits because the directory is brand new. Lore evidence was obtained via web search on spinics/lore mirrors: turn8search3 showed the series being applied on 2026-01-01; turn7search0 and turn7search1 showed active bug-fix traffic in February and March 2026; no retrieved lore hit indicated deprecation or removal. Deployment evidence was obtained via web search results turn9search1 and turn9search4 on Sipeed docs, which show shipping K1-based boards and current OS images. Because the hardware is recent, upstream attention is active, and there is no generic replacement for this SoC PHY block, the correct hint is keep.