From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martin Wetterwald <martin@wetterwald.eu>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Jai Luthra <jai.luthra@ideasonboard.com>,
Gaston Gonzalez <gascoar@gmail.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Stefan Wahren <wahrenst@gmx.net>,
Phil Elwell <phil@raspberrypi.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Umang Jain <uajain@igalia.com>, Kees Cook <kees@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH v2] platform/raspberrypi: vchiq: register bus at subsys_initcall
Date: Thu, 22 Oct 2026 15:31:39 +0200 [thread overview]
Message-ID: <2026102218-vowel-plutonium-629e@gregkh> (raw)
In-Reply-To: <20261022082927.59030-1-martin@wetterwald.eu>
On Thu, Oct 22, 2026 at 10:29:24AM +0200, Martin Wetterwald 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@vger.kernel.org
> Fixes: aa125180c673 ("platform/raspberrypi: Destage VCHIQ interface")
> Reported-by: Martin Wetterwald <martin@wetterwald.eu>
> Closes: https://lore.kernel.org/r/CAFERDQ0FpdVvA5VJxOyRAE_pgxnPVmFx1tkZio5R272j6Bs4tg@mail.gmail.com/
> Reviewed-by: Jai Luthra <jai.luthra@ideasonboard.com>
> Tested-by: Gaston Gonzalez <gascoar@gmail.com> # Raspberry Pi Zero
> Signed-off-by: Martin Wetterwald <martin@wetterwald.eu>
> ---
> Hi Greg,
> this is a regression introduced by aa125180c673 (via your tree) in
> 6.19-rc1 and present in 6.19.y through 7.3.y. If the staging pull for
> 7.4-rc1 has not been sent yet, could you take it there? Otherwise,
> staging-linus would be great. Thanks!
This is not a staging driver anymore, please route it through the proper
tree after -rc1 is out.
thanks,
greg k-h
prev parent reply other threads:[~2026-10-22 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 10:07 [REGRESSION] bcm2835-audio fails to register on vchiq-bus in monolithic kernels since 6.19 (VCHIQ destaging?) Martin Wetterwald
2026-10-12 13:23 ` Thorsten Leemhuis
2026-10-13 4:57 ` Jai Luthra
2026-10-13 7:28 ` Martin Wetterwald
2026-10-13 7:38 ` Martin Wetterwald
2026-10-13 13:14 ` [PATCH] platform/raspberrypi: vchiq: register bus at subsys_initcall Martin Wetterwald
2026-10-13 16:27 ` Jai Luthra
2026-10-15 21:25 ` Gaston Gonzalez
2026-10-16 9:00 ` Martin Wetterwald
2026-10-18 19:52 ` Gaston Gonzalez
2026-10-19 12:26 ` Martin Wetterwald
2026-10-20 19:16 ` Gaston Gonzalez
2026-10-21 19:05 ` Gaston Gonzalez
2026-10-22 8:29 ` [PATCH v2] " Martin Wetterwald
2026-10-22 13:31 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026102218-vowel-plutonium-629e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=gascoar@gmail.com \
--cc=jai.luthra@ideasonboard.com \
--cc=kees@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@wetterwald.eu \
--cc=phil@raspberrypi.com \
--cc=regressions@lists.linux.dev \
--cc=uajain@igalia.com \
--cc=wahrenst@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.