[PATCH v2] platform/raspberrypi: vchiq: register bus at subsys_initcall
Florian Fainelli
florian.fainelli at broadcom.com
Fri Nov 13 19:36:47 PST 2026
From: Florian Fainelli <f.fainelli at gmail.com>
On Thu, 22 Oct 2026 10:29:24 +0200, Martin Wetterwald <martin at wetterwald.eu> wrote:
> Since 6.19-rc1, with CONFIG_BCM2835_VCHIQ=y and CONFIG_SND_BCM2835=y
> (both builtin), the sound cards bcm2835_headphones and bcm2835_hdmi are
> not detected anymore (vc4-hdmi is not affected).
>
> dmesg shows:
>
> Driver 'bcm2835-audio' was unable to register with bus_type
> 'vchiq-bus' because the bus was not initialized.
>
> Since the VCHIQ interface was moved out of staging, its bus is no longer
> guaranteed to be registered before its client drivers. bcm2835-audio,
> still in drivers/staging, registers at device_initcall level and now
> runs first.
>
> Register the bus and the platform driver at subsys_initcall so the bus
> exists before any client driver, independently of link order. The
> platform driver probe already returns -EPROBE_DEFER while the firmware
> is not ready, so probing earlier is safe. When built as modules, this is
> equivalent to module_init() and nothing changes.
>
> Tested on Raspberry Pi 1B rev2, 1B+, 2B, 3B and 4B with VCHIQ and
> bcm2835-audio both builtin and both as modules.
>
> Cc: stable at vger.kernel.org
> Fixes: aa125180c673 ("platform/raspberrypi: Destage VCHIQ interface")
> Reported-by: Martin Wetterwald <martin at wetterwald.eu>
> Closes: https://lore.kernel.org/r/CAFERDQ0FpdVvA5VJxOyRAE_pgxnPVmFx1tkZio5R272j6Bs4tg@mail.gmail.com/
> Reviewed-by: Jai Luthra <jai.luthra at ideasonboard.com>
> Tested-by: Gaston Gonzalez <gascoar at gmail.com> # Raspberry Pi Zero
> Signed-off-by: Martin Wetterwald <martin at wetterwald.eu>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/drivers/fixes, thanks!
--
Florian
More information about the linux-arm-kernel
mailing list