drivers/pinctrl/pxa

Marvell PXA25x/PXA27x pin controller

Pin multiplexing and GPIO configuration logic for Marvell's PXA2xx XScale application processors, the ARM SoCs that powered PDAs, handhelds, and industrial embedded boards from around 2004 onward (including many Palm, HTC, and Zaurus-style devices).

keep-annotate conf=0.79 deploy=low replacement=none subsystem=pinctrl category=platform-vendor
79%

recommendation

Worth keeping but documenting its niche, because the underlying PXA27x silicon dates to 2004 and the modules and eval boards built around it are now marked obsolete at distributors like DigiKey. Even so, upstream maintainers were still reviewing cleanup patches as recently as February 2025, and no replacement driver covers the same SoC block, so removing it would orphan the remaining legacy embedded users still running these chips.

repository signals

6 files
1,321 source lines
6 commits, 5y
+35 / −54 lines added / removed, 5y
4 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 6 total · active in 5/61 months
2021 2022 2023 2024 2025 2026 2021-04: 1 commit · +2 −2 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: 1 commit · +2 −3 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 −2 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: 2 commits · +27 −43 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: 1 commit · +4 −4 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

    The driver still received upstream maintenance in February 2025, with a reviewed pinctrl: pxa2xx cleanup patch.

  2. lore.kernel.org

    The directory also saw earlier maintenance in 2022, indicating occasional but continuing upkeep rather than abandonment.

  3. digikey.com

    A DigiKey module using PXA270 is marked Obsolete and no longer manufactured, indicating the platform is not a current new-design part.

  4. digikey.com

    A PXA270 evaluation board listing is also marked Obsolete, reinforcing that current commercial availability is legacy/surplus rather than mainstream.

  5. en.wikipedia.org

    The PXA27x family dates back to 2004, placing this hardware firmly in a legacy embedded generation.

codex reasoning notes (technical)

Lore evidence came from `mcp__lore_http__.lore_activity` on the three .c files; it showed 2025 maintenance patches and only low-volume activity, with no successful evidence of removal discussion. Deployment evidence came from `web.search_query`: DigiKey listings for PXA270-based modules/eval boards are explicitly obsolete, while Wikipedia (canonical recall page surfaced by web search) dates PXA27x to 2004. Conclusion: hardware is legacy and unlikely in new 2025 products, but upstream still performs occasional fixes/cleanups and there is no natural replacement driver for the same SoC block, so annotate rather than deprecate/remove.