From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.222.51 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1792609511; b=zriJM+aXys4lhoicG4iTBHL0gY7guarHlsiyX9GxYqZGQfhCqON0qa4/AaEXPQsbP/YE e8Ho8B2y8UfzhN2+IUZhqRaOZz5gziP2+G85Zr8XPN+yCepQocRwgoWtCOI9w4DDtas/P IT1j9JhvNlfp728iqt9o8xI9qJ27PbWPKYOG8P6kuhFvfb2rAn+M3qRwfe5/p+lmDunwU B75FO+c55p88vVInCIYU2A64OSpi2EF2gek0wI2lOLga5HdVWtCzSGIRmF44+zgMEMUB8 ZZHLi92qTpU73b6TcJO3waC0Dzi5faIokQZtxexfUwQ2mohHBPcGkUHkX8M2EkW8gDw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792609511; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: Mime-Version:Content-Transfer-Encoding:Content-Type:Date:Message-Id: From:To:Cc:Subject:X-Mailer:References:In-Reply-To; bh=yaJdLtbHiyXcMFgqBwOm4F2HMHkjIk9pI39u14xSXTs=; b=4TJyrplZ25/IdduJ99esf7q4SAdFMygKoOVgzxFz6+PzA8uFP7s1Oix5ZkTDz+A6v4oW SJAc0TK7PizvcZs/INeSiZy3xoFUVNRO96IdAseKr2vKNe3Hx652c/d3pdQIZAmoi41GB 2OCv8bPlmDFUwfeW9ohd05H1ET/fvzhrIY0PNRy9oxzZs48LLzvgDys4raYH949cMJIbW thnqzRk317UJnoUYn12ugwl0VwDgrQ1MV5mlZnq4zuByGmlGzlj8KMHojAQy8JY9/tlN1 ay2X3CB7ds2JSRLfKqGbaunvgDEvECDEO0LiHVtZvX4/rU6hKbDWUH+e2Ks9Q9ngk2A== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=Bzo0us2z; arc=none smtp.remote-ip=209.85.222.51 Received: from mail-ua1-f51.google.com (mail-ua1-f51.google.com [209.85.222.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DEB83606A31B for ; Wed, 21 Oct 2026 19:05:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org DEB83606A31B Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=Bzo0us2z Received: by mail-ua1-f51.google.com with SMTP id a1e0cc1a2514c-988c1727b83so28638241.3 for ; Wed, 21 Oct 2026 12:05:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1792609510; x=1793214310; darn=lists.linux.dev; h=in-reply-to:references:subject:cc:to:from:message-id:date :content-type:content-transfer-encoding:mime-version:from:to:cc :subject:date:message-id:reply-to:content-type; bh=yaJdLtbHiyXcMFgqBwOm4F2HMHkjIk9pI39u14xSXTs=; b=Bzo0us2z2Xu+EhcPrskPoOfVFz1MD9dIXgEeIa07Q76S4nTSk6XCr4KJPZcM3aGozn +XvL6unGMlGcoMLatAiS85JFCY+QLd4CLQGSN2NIJmn/ToVIys3n3L/cp1iLTk/nHRSF UrkKNeVs7YH78eQFApUKA5XELlQ+36JtCxz8BESHey3FfrY4NhAMq9UJPDExAEBGRtnN a8G3zEo2XAbA3C0NN3jNw+uQgpGta/Jo8GizmcBWz2ljpU2201DKBASICtO5nZf0hu4l NdRLYxn0k60B/LuASiAJx2aRpnH3wX/nITorwZTnKphMQedDSPWJ6kSMYPy5XYFcFuVR oCXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792609510; x=1793214310; h=in-reply-to:references:subject:cc:to:from:message-id:date :content-type:content-transfer-encoding:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=yaJdLtbHiyXcMFgqBwOm4F2HMHkjIk9pI39u14xSXTs=; b=vwn+Him8N17WXSSz3jZJ6gyVMwzwwCRhGZEb8xcrk4trYS3jP1si0ZrQZzWhZ7q2XO +lC8hAfLKIedL1Di2VlGUseUs+DRzyYi2O1K0jJxJ476LwCbo4LHMNMf/OfzwUwkvJFL xt0f0vdn95+09wTKK7a+ekjU1tm2FVoBmjwSDj22hE+/g1XDvwrjuPVxU5W41fw3D4+O X5+0n62Me7P20UbT+fCr87dh03Xt7KAHsM+bxEtdwHuxEbGlujBVKtkf4iywTk9Sn3qD i/+m7KN2RfjqFOvipyQnvr0gix+HHE10KaW0F0alHi2+rG0SlRvaxioJxktoXgNcLMTz e6EQ== X-Forwarded-Encrypted: i=1; AKwUvBzpqJ0xqRvrOOcd/qUmqhvO88QfHZZWtwyYungwixcqKGrDmL8JM6Zt33HXCHCJ76sF2blewVLlrgh/LN6P@lists.linux.dev X-Gm-Message-State: AFq9FYJeanDQN5rUlCWQAiNH5IjOCxedoKd8UgPbd+PyLoBECfho5qPH z5WbcBQ/ihsfWhYDs+i7MBQ2zEKbHj57UOnDpS1h8ObO8ecjNRYOlGk8 X-Gm-Gg: AYBFou04aijjKuu2DzSw/yMBB0h2dq1rw+RcRMpbFh7kgNcImsHV5rXfnjgMUFxWcRY 3IOjTF8yNfaqEhOXbwp1Ce0a+T0Ubij1i/ugZV10R2yZyHvjiSnRF21Q+MSjFwvab5MWu6IKIeQ fSQZUA97JoBh5Uq7Bp/n/UUvoi38MMOJSb+b6OrbCUC/UHKPaktP7gV/FyjxNeHTDWLUucCOCD/ cVRPiz2Z4GljKCv2irLvjU3lGv14oc5uIEUn/jIC40OMuXDByeqn9080jtAhlokw8COrfBODHTz r9i12s6a5WknT0u7JsOUKFDT+tmP4uuzPK34Clr79NDpzxRv//O+4db62rCKMajoKfORzdJ/83j J+i0UwetIN3tBO1s+S/5eFrc3lWsXpppAas9M+I/81ncI88xwujqtMbmJRTvwP4o6sx/X96JdNx +nrKKI6egwSvmaoL4NcaSCvZfnFMWSGGrBmsL1QPLoHHaW8MA06JZ72Mu1aUdRyk1Ng86BmwEuP X912i2n5Ey7WUfa7q+jhTsLKesn7Mk3GiE9lz36Ps9+7X8+3so= X-Received: by 2002:a05:6102:3e92:b0:7c3:83a9:edc9 with SMTP id ada2fe7eead31-7cc92461809mr1156246137.1.1792609509675; Wed, 21 Oct 2026 12:05:09 -0700 (PDT) Received: from localhost ([2802:8012:39:ac00:85dd:f0f7:d2d2:5158]) by smtp.gmail.com with ESMTPSA id ada2fe7eead31-7cc921b6094sm3818360137.1.2026.10.21.12.05.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Oct 2026 12:05:09 -0700 (PDT) X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 21 Oct 2026 16:05:03 -0300 Message-Id: From: "Gaston Gonzalez" To: "Martin Wetterwald" Cc: "Florian Fainelli" , "Broadcom internal kernel review list" , "Jai Luthra" , "Greg Kroah-Hartman" , "Stefan Wahren" , "Phil Elwell" , "Laurent Pinchart" , "Umang Jain" , "Kees Cook" , , , , , Subject: Re: [PATCH] platform/raspberrypi: vchiq: register bus at subsys_initcall X-Mailer: aerc 0.20.0 References: <20261013131435.1454019-1-martin@wetterwald.eu> In-Reply-To: On Mon Oct 19, 2026 at 9:26 AM -03, Martin Wetterwald wrote: > On Sun, Oct 18, 2026 at 9:53=E2=80=AFPM Gaston Gonzalez wrote: > >> Running 'speaker-test -t wav -D plughw:1,0 -c 2' crash the system, so >> thinks seem not to be working with that interface. >> >> Im trying to debug what happens in that condition; I will need a couple >> of days I guess. So far, this is what I could check. >> >> Any feedback on the test or debugging would be appreciated. > > Hi Gaston, > Thanks for digging into this. > > The patch only changes when the VCHIQ bus and driver are registered durin= g > boot. So it's enough to check these two cases to validate the patch: > - without my patch: dmesg shows the "unable to register with bus_type > 'vchiq-bus'" error, and bcm2835_hdmi is absent from /proc/asound/cards. > - with my patch: the error is gone and bcm2835_hdmi is present in > /proc/asound/cards. > > (Since the Pi Zero has no Headphones jack, you need to test both cases wi= th > snd_bcm2835.enable_hdmi=3D1 in the command line. Otherwise the card never= shows > up, even when everything works.) > > Could you check these two cases? > Hi Martin, Results on the two cases: Case 1:=20 - dmesg shows 'Driver bcm2835-audio was unable to register with bus type 'vchiq-bus' because the bus was not initialized'. - cat /proc/asound/cards shows only: vc4hdmi. Case 2: - dmesg does not show 'Driver bcm2835-audio was unable to register..' - cat /proc/asound/cards now shows: 0 [vc4hdmi ]: vc4-hdmi - vc4-hdmi vc4-hdmi 1 [HDMI ]: bcm2835_hdmi - bcm2835 HDMI bcm2835 HDMI So your patch works on the Raspberry Pi Zero v1.3. Regards, Gaston > > Testing that you can hear the sound going through bcm2835-audio is a full > functional test that goes even further than the patch: it does not only t= est > bus registration but also that the audio driver is working. > > On my side, without vc4-drm, I can successfully hear sound through both b= cm2835 > Headphones and bcm2835 HDMI: > > # aplay -l > **** List of PLAYBACK Hardware Devices **** > card 0: HDMI [bcm2835 HDMI], device 0: bcm2835 HDMI [bcm2835 HDMI] > [...] > card 0: HDMI [bcm2835 HDMI], device 1: IEC958 [IEC958] > [...] > card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 > Headphones [bcm2835 Headphones] > [...] > > # speaker-test -D plughw:0,0 # (HDMI) > > # speaker-test -D plughw:1,0 # (Headphones, not on the Pi Zero) > > > If you still want to output sound through bcm2835_hdmi (optional): > > There can only be one owner of the HDMI port: either the firmware or the > kernel. > When the Raspberry Pi boots, the firmware first owns the HDMI and display= s a > rainbow splash. Then it launches Linux. > > There are 2 ways for the kernel to deal with the video output: > > 1) With vc4-drm (CONFIG_DRM_VC4), the kernel takes over the HDMI controll= er > from the firmware and handles everything itself (this is your case). > 2) With simple-framebuffer (CONFIG_DRM_SIMPLEDRM or CONFIG_FB_SIMPLE), th= e > kernel leaves the HDMI to the firmware and just writes pixels to a > memory area > (the framebuffer) set up by the firmware. > > I get a similar problem on my side when sending sound through bcm2835_hdm= i with > vc4-drm loaded: my screen shuts down (but the kernel is still alive). > It most likely comes from the firmware and the kernel both trying to driv= e the > same HDMI port: with vc4-drm, the kernel owns the HDMI controller, and th= e > firmware (which bcm2835-audio talks to through VCHIQ) is not supposed to = touch > it. > > A simple way to output sound through bcm2835_hdmi is to not use the vc4-d= rm > driver at all, and use simple-framebuffer if you still want a display. > > To remove vc4-drm: > - Do not compile the driver into the kernel (CONFIG_DRM_VC4=3Dn) or black= list the > module. > - Remove any vc4 overlay in config.txt file (e.g. remove dtoverlay=3Dvc4-= kms-v3d). > > To enable simple-framebuffer, use one of the two configs: > > CONFIG_DRM=3Dy > CONFIG_DRM_SIMPLEDRM=3Dy > CONFIG_DRM_FBDEV_EMULATION=3Dy > CONFIG_FRAMEBUFFER_CONSOLE=3Dy > > or, the older way: > > CONFIG_FB=3Dy > CONFIG_FB_SIMPLE=3Dy > CONFIG_FRAMEBUFFER_CONSOLE=3Dy > > (FRAMEBUFFER_CONSOLE=3Dy, and DRM_FBDEV_EMULATION in the DRM case, are on= ly > needed to see the boot messages on the screen, with console=3Dtty1 on the= command > line.) > > If you have remote access to your Pi Zero (either through network+SSH or > through serial console), you actually don't even need the simple-framebuf= fer: > you can just remove vc4-drm, and let the firmware display its rainbow spl= ash on > the HDMI port. > Then you can login to your Pi Zero through SSH for example and launch > speaker-test. > As long as the HDMI video output is active, it's enough for the sound to = be > able to go through, even if the image was not drawn by Linux. > > But again, this full functional test is optional. > > Regards, > Martin