SpacemiT K1 and K3 RISC-V SoC pin controller
Configures pin muxing and I/O settings on SpacemiT's K1 and K3 octa-core RISC-V application processors, which debuted around 2024 and are used in budget RISC-V developer boards such as the Banana Pi BPI-F3 SBC and the BPI-CM6 compute module sold in 2025 and 2026.
recommendation
It should stay because this is the active upstream pin-multiplexing driver for SpacemiT's K1 and K3 RISC-V SoCs, which power currently shipping single-board computers like the Banana Pi BPI-F3 and the 2025 BPI-CM6 module. Local git history shows substantive feature work and fixes landing from late 2024 into early 2026, including new K3 support, and no removal discussions surfaced upstream.
repository signals
sources
- devicetree.org
The upstream binding covers both `spacemit,k1-pinctrl` and `spacemit,k3-pinctrl`, matching this driver’s supported compatibles.
- cateee.net
LKDDb shows CONFIG_PINCTRL_SPACEMIT_K1 in mainline kernels 6.13 through 6.19-rc/HEAD and lists both `spacemit,k1-pinctrl` and `spacemit,k3-pinctrl` compatibles.
- wiki.banana-pi.org
Banana Pi documents the BPI-F3 as a currently marketed board based on the SpacemiT K1 SoC.
- bpi-shop.com
The BPI-F3 product page shows the SpacemiT K1 board available for purchase, supporting new-hardware availability.
- forum.banana-pi.org
Banana Pi announced a 2025 BPI-CM6 computer module based on SpacemiT K1, indicating continuing platform rollout beyond a single dev board.
- forum.banana-pi.org
The Banana Pi BPI-F3/BPI-CM6 forum category had activity into 2026, suggesting ongoing user/developer deployments rather than abandonment.
codex reasoning notes (technical)
Real driver, not an asset/helper dir. Local source inspection (`sed`, `rg`) shows a platform pinctrl driver with OF matches for K1 and K3, and local git history (`git -c safe.directory=... log`) shows substantive fixes/features from 2024-10 through 2026-01, including K3 support and I/O power-domain work; that is active upstream maintenance, not removal. I could not use the promised lore MCP because no such server was exposed here, and `lei` was unavailable; a targeted web search over `lore.kernel.org` returned no removal-discussion hits, so there is no evidence to escalate toward remove. Deployment looks niche but real: current Banana Pi board/shop/forum pages obtained via web search show K1-based SBC/SoM hardware on sale and discussed in 2025-2026. The devicetree schema URL came directly from the local binding file `$id`; LKDDb and Banana Pi pages came from web search. Because this is a recently upstreamed SoC pinctrl block with active follow-on enablement and no generic substitute, the recommendation is keep.