Greybus modular device interconnect for BeaglePlay and BeagleConnect
Greybus is a transport protocol originally created for Google's modular Project Ara smartphone, letting a host hot-plug modules (sensors, GPIO, I2C, UART, audio, lights) over a UniPro link. After Ara was cancelled in 2016 it found a second life in the BeagleBoard ecosystem, where BeaglePlay boards and BeagleConnect Freedom wireless sensor modules use it as their module-to-host plumbing.
recommendation
Worth keeping but documenting its niche, because although the original Project Ara phone platform was cancelled in 2016, Greybus is still actively maintained in the kernel and continues to ship as the module architecture behind currently sold BeagleBoard hardware like BeaglePlay and BeagleConnect Freedom. Commit activity through 2024-2026 and named maintainers in MAINTAINERS show this is a living subsystem, just one serving a small embedded/IoT audience rather than the mass market it was first designed for.
repository signals
sources
- git.kernel.org
Upstream Greybus staging code is still seeing regular fixes and cleanup, matching the local tree's 2024-2026 commit activity rather than abandonment or removal prep.
- docs.kernel.org
Current kernel MAINTAINERS lists both drivers/greybus/ and drivers/staging/greybus/ as Maintained, with named maintainers for the subsystem and multiple subdrivers.
- docs.beagleboard.org
BeagleBoard's current Greybus overview says Project Ara is discontinued but Greybus is still used, describing BeagleConnect as an active Greybus-based embedded/IoT stack.
- docs.beagleboard.org
Current BeaglePlay + BeagleConnect documentation describes Greybus as the active host/module architecture for BeaglePlay and BeagleConnect Freedom deployments.
- beagleboard.org
BeaglePlay is currently marketed for purchase, indicating Greybus-backed hardware is still sold new after 2025, albeit in a niche embedded market.
- en.wikipedia.org
Project Ara, Greybus's original flagship platform, was cancelled in 2016, so mainstream phone-volume deployment did not materialize.
codex reasoning notes (technical)
No early-exit: this directory contains real module_init/module_greybus_driver hardware drivers. Activity first grounded with local shell inspection (`rg`, `git -c safe.directory=... log`) showing substantive 2024-2026 fixes and TODO cleanup; I cite the canonical kernel.org log URL for that same path by canonical recall. I used web search to obtain docs.kernel.org MAINTAINERS, which shows the subsystem is still maintained, and current BeagleBoard docs/pages showing live BeaglePlay/BeagleConnect Greybus deployments and product availability. I used web search to obtain Wikipedia's Project Ara page for the original-market cancellation context. I found no removal discussion in web/lore searching, so active maintenance plus niche current hardware argues against deprecate/remove; annotate instead because deployments appear specialized and low-volume rather than broad.