Raspberry Pi BCM2835 Built-in Audio (3.5mm jack and HDMI)
Provides ALSA sound output for the built-in 3.5mm analog headphone jack and HDMI audio on Raspberry Pi boards based on Broadcom's BCM2835 family (Pi 1, Pi Zero, Pi Zero 2 W, and related models). Audio is routed through the VideoCore GPU's VCHIQ message interface to the closed firmware that actually drives the audio hardware.
recommendation
Worth keeping but its staging status should be documented because, although the hardware is widely deployed on Raspberry Pi boards still sold new (the Pi 4 is in production through 2034 and the Pi Zero 2 W through 2030) and the code is still being touched as recently as November 2025, it has lingered in drivers/staging for years and depends on the proprietary VideoCore VCHIQ firmware interface. That combination argues against either promotion out of staging or removal — annotation is the honest middle ground.
repository signals
sources
- cateee.net
LKDDb maps CONFIG_SND_BCM2835 to drivers/staging/vc04_services/bcm2835-audio and describes it as the BCM2835 built-in audio driver using VCHIQ for 3.5mm and HDMI audio.
- raspberrypi.com
Raspberry Pi 4 Model B is still in production until at least January 2034 and exposes stereo audio plus HDMI outputs relevant to this driver family.
- raspberrypi.com
Raspberry Pi Zero 2 W is still in production until at least January 2030 and remains a current Raspberry Pi deployment target with HDMI-capable built-in multimedia hardware.
codex reasoning notes (technical)
Real driver directory: ALSA module snd-bcm2835 with Kconfig help stating it handles 3.5mm and HDMI audio through VCHIQ. Upstream activity was checked locally via shell using git log on this path; there are substantive touches through 2025-11-09 and no visible local-history sign of an active removal series, so removal/deprecate would be too aggressive. Cited URLs were obtained via web.search_query results: LKDDb for driver identity/deployment surface, and official Raspberry Pi product pages for ongoing sale/production evidence. Lore MCP was unavailable in this environment, and a web lore search did not surface a removal discussion. Staging status and firmware dependency argue for annotation rather than promotion, but continuing maintenance plus still-sold hardware argue to keep.