linux-drivers/
drivers/greybus

Greybus subsystem for BeaglePlay and Project Ara devices

Greybus is a hardware-agnostic bus protocol originally designed for Google's Project Ara modular smartphone, allowing hot-pluggable modules to communicate over the UniPro transport. After Ara was cancelled it found a second life on BeagleBoard hardware: the BeaglePlay single-board computer uses Greybus over a CC1352P7 wireless coprocessor to talk to BeagleConnect Freedom sensor modules.

keep-annotate conf=0.85 last_sold=2026 deploy=low replacement=none subsystem=greybus category=bus-other
85%

recommendation

Worth keeping but documenting as a niche subsystem, since its original Project Ara use case was discontinued years ago and the only currently shipping platform built on it is the BeagleBoard ecosystem (BeaglePlay plus BeagleConnect Freedom modules). Upstream activity is still real however, with bug fixes landing in early 2026 and feature work in late 2025, and BeaglePlay remains for sale, so removal would break a small but live user base.

repository signals

18 files
10,519 source lines
36 commits, 5y
+1,376 / −166 lines added / removed, 5y
24 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 36 total · active in 23/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: 1 commit · +1 −1 2022-01: 0 commits · +0 −0 2022-02: 3 commits · +18 −8 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: 1 commit · +2 −1 2022-12: 0 commits · +0 −0 2023-01: 1 commit · +7 −7 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +3 −3 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: 2 commits · +514 −0 2023-11: 0 commits · +0 −0 2023-12: 4 commits · +55 −26 2024-01: 3 commits · +20 −21 2024-02: 2 commits · +36 −6 2024-03: 0 commits · +0 −0 2024-04: 1 commit · +1 −0 2024-05: 0 commits · +0 −0 2024-06: 1 commit · +2 −0 2024-07: 1 commit · +2 −2 2024-08: 0 commits · +0 −0 2024-09: 1 commit · +647 −13 2024-10: 1 commit · +2 −2 2024-11: 1 commit · +1 −1 2024-12: 0 commits · +0 −0 2025-01: 1 commit · +3 −1 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 1 commit · +1 −1 2025-05: 1 commit · +2 −1 2025-06: 1 commit · +8 −17 2025-07: 0 commits · +0 −0 2025-08: 1 commit · +2 −1 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 2 commits · +7 −7 2025-12: 0 commits · +0 −0 2026-01: 1 commit · +10 −12 2026-02: 4 commits · +32 −35 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Recent non-treewide bug-fix traffic hit gb-beagleplay in March 2026, indicating active upstream maintenance.

  2. lore.kernel.org

    Another gb-beagleplay fix was posted in April 2026 and cc'd to stable, showing current support demand.

  3. lore.kernel.org

    Greybus core/module code saw feature work in late 2025, not just janitorial churn.

  4. beagleboard.org

    BeaglePlay had a live product page with purchase links and 2026 software images, supporting that Greybus-backed hardware is still sold new.

  5. docs.beagleboard.org

    Official BeagleBoard docs describe BeaglePlay's AM62x + CC1352P7 Greybus architecture and BeagleConnect Freedom module use.

  6. docs.beagleboard.org

    Official docs say Greybus originated with Project Ara, which is discontinued, underscoring that the subsystem is now niche outside newer BeagleBoard deployments.

codex reasoning notes (technical)

Obtained lore URLs via lore_activity on drivers/greybus/gb-beagleplay.c and drivers/greybus/module.c; those results show 2025-2026 fixes and feature patches, with no removal signal. Obtained BeagleBoard URLs via web search_query; they show current BeaglePlay sale/support and Greybus-based BeagleConnect deployments. Conclusion: hardware is niche and legacy-Ara-derived, but there is still real upstream attention and at least one currently sold platform, so keep the driver but annotate it as low-deployment/specialized rather than deprecate.