Greg Kroah-Hartman gregkh@linuxfoundation.org writes:
On Fri, Sep 18, 2026 at 03:43:20PM +0300, Dan Carpenter wrote:
On Fri, Sep 18, 2026 at 07:18:54AM -0500, Alex Elder wrote:
On 9/17/26 8:14 PM, Ethan Nelson-Moore wrote:
The Greybus camera driver has been marked as BROKEN since commit d4f56b47a8fa ("staging: greybus: Add drivers/staging/greybus to the build"). It has not been able to compile since at least commit ec0ad868173d ("staging: greybus: move core include files to include/linux/greybus/") because it includes greybus_protocols.h from its own directory. These two facts make it very clear there is no demand for this driver. Remove it from the kernel.
Hmmm. Do you know why it is BROKEN? Do you know what it would take to make it work? I understand the point of removing it, but in part the Greybus code has historically served as sample code for people to work on. It might be nicer to have fixing it be a pet project.
The compile breaks because of:
commit aa1b4da6af67d5c6a4e933c2d30890c6f282f505 Author: Boris Brezillon bbrezillon@kernel.org Date: Mon Nov 10 14:28:35 2014 -0300
[media] v4l: Forbid usage of V4L2_MBUS_FMT definitions inside the kernelPlace v4l2_mbus_pixelcode in a #ifndef __KERNEL__ section so that kernel users don't have access to these definitions.
Good point, no one has picked this up since then so let's drop the driver and if it ever is needed in the future it can be reverted and brought back.
Just wanted to chime in, that there has been some work on audio and camera protocols on the Zephyr side as part of Google Summer of Code 2026 [0]. With that said, the work never truly interacted with the kernel driver. I would like to at some point, but I don't really have the bandwidth at the moment. So it seems reasonable as well.
thanks,
greg k-h _______________________________________________ greybus-dev mailing list -- greybus-dev@lists.linaro.org To unsubscribe send an email to greybus-dev-leave@lists.linaro.org
[0]: https://forum.beagleboard.org/t/gsoc-2026-final-report-greybus-camera-audio-...
NOTE: recently switched mailing clients, and it replied from incorrect account which was not in mailing list. So you might see similar email again if it get's approved or something instead of being cancelled.
Best Regards, Ayush Singh