From: Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp>
To: stefan.wahren@i2se.com
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
978025@bugs.debian.org, bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org, 985928@bugs.debian.org
Subject: Re: Sound issues with the 5.10.x kernel (alsa)
Date: Mon, 29 Mar 2021 08:13:25 +0900 (JST) [thread overview]
Message-ID: <20210329.081325.1881666155034010044.ryutaroh@ict.e.titech.ac.jp> (raw)
In-Reply-To: <7a123105-8c2e-e831-9466-3d8afc96aa8e@i2se.com>
Hi Stefan, thank you for your response.
> i assume you set this option in the config.txt? This shouldn't have any
> affect for the mainline kernel / DT.
I am aware of that...
I did "snd_bcm2835 enable_hdmi=0" in /etc/modules.
"modinfo snd_bcm2835" shows as below. Doesn't it indicate snd_bcm2835 having
an option enable_hdmi???
It seems that the contention of grabbing HDMI audio output between vc4.ko
and snd_bcm2835.ko can be addressed if snd_bcm2835.ko honors the
option enable_hdmi with its default =0, but currently enable_hdmi seems
having no effect in behavior of snd_bcm2835...
# modinfo snd_bcm2835
filename: /lib/modules/5.10.0-5-rt-arm64/kernel/drivers/staging/vc04_services/bcm2835-audio/snd-bcm2835.ko
alias: platform:bcm2835_audio
license: GPL
description: Alsa driver for BCM2835 chip
author: Dom Cobley
depends: snd-pcm,vchiq,snd
staging: Y
intree: Y
name: snd_bcm2835
vermagic: 5.10.0-5-rt-arm64 SMP preempt_rt mod_unload modversions aarch64
sig_id: PKCS#7
signer: Debian Secure Boot CA
sig_key: 4B:6E:F5:AB:CA:66:98:25:17:8E:05:2C:84:66:7C:CB:C0:53:1F:8C
sig_hashalgo: sha256
signature: omitted, too long.
parm: force_bulk:Force use of vchiq bulk for audio (bool)
parm: enable_hdmi:Enables HDMI virtual audio device (bool)
parm: enable_headphones:Enables Headphones virtual audio device (bool)
parm: enable_compat_alsa:Enables ALSA compatibility virtual audio device (bool)
parm: num_channels:Number of audio channels (default: 8) (int)
Best regards, Ryutaroh
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2021-03-28 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3165951.nLcn7dHqa8@bagend>
2021-02-08 12:22 ` Sound issues with the 5.10.x kernel (alsa) Stefan Wahren
2021-02-08 12:50 ` Diederik de Haas
2021-02-16 0:12 ` Diederik de Haas
2021-02-16 14:38 ` Diederik de Haas
2021-03-28 0:48 ` Ryutaroh Matsumoto
2021-03-28 5:58 ` Ryutaroh Matsumoto
2021-03-28 9:29 ` Stefan Wahren
2021-03-28 23:13 ` Ryutaroh Matsumoto [this message]
2021-03-28 23:17 ` Ryutaroh Matsumoto
[not found] ` <20210208.230026.1706784668119437570.ryutaroh@ict.e.titech.ac.jp>
2021-02-08 14:31 ` Diederik de Haas
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=20210329.081325.1881666155034010044.ryutaroh@ict.e.titech.ac.jp \
--to=ryutaroh@ict.e.titech.ac.jp \
--cc=978025@bugs.debian.org \
--cc=985928@bugs.debian.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).