- Alsa-devel - mailman.alsa-project.org

snd_seq_open and pulse audio??
by Mark Lentczner 01 Dec '24

01 Dec '24

My ALSA Seq port manager runs as a service. The service is installed under its own service user, which has the home directory set to some place non-existent and non-writable. When my service starts I see this surprising log message: *amidiminder[136345]: Failed to create secure directory (/var/lib/misc/.config/pulse): No such file or directory* A little investigation reveals that this error is generated by this call, opening the ALSA Seq: serr = snd_seq_open(&seq, "default", SND_SEQ_OPEN_DUPLEX, 0); It's a little surprising that opening ALSA Seq would somehow invoke something in pulse audio, and further that pulse audio would then be trying to create its user directory (.configure/pulse is where pulse audio sticks things under each user's home directory). This seems to be a reprise of this Debian bug from 2013 involving alsa-utils and pulse audio: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712980 Which was close via this patch to alsa-utils: alsactl: Make homedir configurable <https://mailman.alsa-project.org/hyperkitty/list/alsa-devel@alsa-project.or…> The fix there seems to be adding some mechanism to change the $HOME environment variable to point at /var/run/alsa. I agree with Takashi's reply to that fix: Overriding $HOME sounds scary to me, too! Is there any insight into this... and did that fix stick or was some other method found to deal with this. In my case, I don't understand why just opening the ALSA Seq is causing any pulse audio code to run... but perhaps things are more entwined at a lower level of ALSA lib than I understand. - Mark

1 0

Linux Mint Cinnamon 22 Soundblaster AE-9 no sound
by GitHub issues - opened 30 Nov '24

30 Nov '24

alsa-project/alsa-lib issue #424 was opened from Starfoxfs: Hi, i have fresh installed Linux Mint Cinnamon 22 Kernel 6.8.0.49-generic I can´t get the Soundblaster AE-9 to work. Creative Labs has no Drivers for Linux and points to the alsa community. Is there any change to get support for the Soundblaster AE-9 in the future ? I think the big Problem is the external DAC for Headphones from the Soundblaster AE-9. In Windows this "clicks" on startup and activates the DAC, but in Linux this is all dead. Issue URL : https://github.com/alsa-project/alsa-lib/issues/424 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

arecordmidi.1: Some remarks and editorial changes for this man page
by Bjarni Ingi Gislason 30 Nov '24

30 Nov '24

Package: alsa-utils Version: 1.2.12-1 Severity: minor Tags: patch * What led up to the situation? Checking for defects with test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page" [Use "groff -e ' $' <file>" to find trailing spaces.] ["test-groff" is a script in the repository for "groff"; is not shipped] (local copy and "troff" slightly changed by me). [The fate of "test-nroff" was decided in groff bug #55941.] * What was the outcome of this action? troff: backtrace: file '<stdin>':69 troff:<stdin>:69: warning: trailing space in the line troff: backtrace: file '<stdin>':77 troff:<stdin>:77: warning: trailing space in the line Output from "test-nroff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z ": troff: backtrace: file '<stdin>':69 troff:<stdin>:69: warning: trailing space in the line troff: backtrace: file '<stdin>':77 troff:<stdin>:77: warning: trailing space in the line * What outcome did you expect instead? No output (no warnings). -.- General remarks and further material, if a diff-file exist, are in the attachments. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.11.10-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii kmod 33+20240816-2 ii libasound2t64 1.2.12-1+b1 ii libatopology2t64 1.2.12-1+b1 ii libc6 2.40-3 ii libfftw3-single3 3.3.10-1+b3 ii libncursesw6 6.5-2+b1 ii libsamplerate0 0.2.2-4+b2 ii libtinfo6 6.5-2+b1 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: pn dialog <none> -- no debconf information

1 0

[tiwai-sound:for-next 6/10] sound/core/ump.c:1259:69: warning: '%s' directive output may be truncated writing up to 11 bytes into a region of size between 4 and 22
by kernel test robot 29 Nov '24

29 Nov '24

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next head: 9b5f8ee43e48c25fbe1a10163ec04343d750acd0 commit: e29e504e7890b9ee438ca6370d0180d607c473f9 [6/10] ALSA: ump: Indicate the inactive group in legacy substream names config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20241130/202411300103.FrGuTAYp-lkp@…) compiler: alpha-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241130/202411300103.FrGuTAYp-lkp@…) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <lkp(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202411300103.FrGuTAYp-lkp@intel.com/ All warnings (new ones prefixed by >>): sound/core/ump.c: In function 'fill_substream_names': >> sound/core/ump.c:1259:69: warning: '%s' directive output may be truncated writing up to 11 bytes into a region of size between 4 and 22 [-Wformat-truncation=] 1259 | snprintf(s->name, sizeof(s->name), "Group %d (%.16s)%s", | ^~ sound/core/ump.c:1259:17: note: 'snprintf' output between 11 and 40 bytes into a destination of size 32 1259 | snprintf(s->name, sizeof(s->name), "Group %d (%.16s)%s", | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1260 | idx + 1, name, | ~~~~~~~~~~~~~~ 1261 | ump->groups[idx].active ? "" : " [Inactive]"); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ vim +1259 sound/core/ump.c 1246 1247 static void fill_substream_names(struct snd_ump_endpoint *ump, 1248 struct snd_rawmidi *rmidi, int dir) 1249 { 1250 struct snd_rawmidi_substream *s; 1251 const char *name; 1252 int idx; 1253 1254 list_for_each_entry(s, &rmidi->streams[dir].substreams, list) { 1255 idx = ump->legacy_mapping[s->number]; 1256 name = ump->groups[idx].name; 1257 if (!*name) 1258 name = ump->info.name; > 1259 snprintf(s->name, sizeof(s->name), "Group %d (%.16s)%s", 1260 idx + 1, name, 1261 ump->groups[idx].active ? "" : " [Inactive]"); 1262 } 1263 } 1264 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

amd-soundwire: add support for AMD generic legacy machine driver
by GitHub pull_request - opened 29 Nov '24

29 Nov '24

alsa-project/alsa-ucm-conf pull request #478 was opened from perexg: The card components string is similar to Intel's SOF driver like, so we can reuse sof-soundwire configuration and it is logical to reduce future maintenance, because the chips connected to soundwire bus are similar for multiple PCI bridges. Example of the components string: Components : ' cfg-amp:1 hs:rt722 spk:rt722 mic:rt722' Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/478 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/478.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[GIT PULL] ASoC fixes for v6.13-merge-window
by Mark Brown 28 Nov '24

28 Nov '24

The following changes since commit 82ff5abc2edcfba0c0f1a1be807795e2876f46e9: ASoC: hdmi-codec: reorder channel allocation list (2024-11-15 13:43:00 +0000) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.13-merge-window for you to fetch changes up to b682aa788e5f9f1ddacdfbb453e49fd3f4e83721: ASoC: amd: yc: Add a quirk for microfone on Lenovo ThinkPad P14s Gen 5 21MES00B00 (2024-11-27 13:45:45 +0000) ---------------------------------------------------------------- ASoC: Fixes for v6.13 A pile of driver specific quirks and fixes that came in since the merge window. One of the AMD fixes is a bit broken for some systems, I'm expecting an incremental change to fix that but it seems better overall to merge the rest of the fixes. There's also one small documentation update that seemed sensible to apply now, pointing to the dapm-graph tool. ---------------------------------------------------------------- Alex Far (1): ASoC: amd: yc: fix internal mic on Redmi G 2022 Bard Liao (1): ASoC: SOF: ipc3-topology: Convert the topology pin index to ALH dai index Charles Han (1): ASoC: imx-audmix: Add NULL check in imx_audmix_probe Ilya Zverev (1): ASoC: amd: yc: Add a quirk for microfone on Lenovo ThinkPad P14s Gen 5 21MES00B00 Mario Limonciello (1): ASoC: amd: Fix build dependencies for `SND_SOC_AMD_PS` Nícolas F. R. A. Prado (1): ASoC: mediatek: Check num_codecs is not zero to avoid panic during probe Uwe Kleine-König (1): ASoC: amd: yc: Add quirk for microphone on Lenovo Thinkpad T14s Gen 6 21M1CTO1WW Venkata Prasad Potturu (1): ASoC: amd: yc: Fix for enabling DMIC on acp6x via _DSD entry anish kumar (1): ASoC: doc: dapm: Add location information for dapm-graph tool liujing (1): ASoC: apple: Fix the wrong format specifier Documentation/sound/soc/dapm.rst | 3 ++ sound/soc/amd/Kconfig | 1 + sound/soc/amd/yc/acp6x-mach.c | 39 +++++++++++++++++++++- sound/soc/apple/mca.c | 2 +- sound/soc/fsl/imx-audmix.c | 3 ++ sound/soc/mediatek/mt8188/mt8188-mt6359.c | 9 +++-- .../mediatek/mt8192/mt8192-mt6359-rt1015-rt5682.c | 4 +-- sound/soc/mediatek/mt8195/mt8195-mt6359.c | 9 +++-- sound/soc/sof/ipc3-topology.c | 26 +++++++++++++-- 9 files changed, 86 insertions(+), 10 deletions(-)

2 1

aplay.1: Some remarks and editorial changes for this man page
by Bjarni Ingi Gislason 27 Nov '24

27 Nov '24

Package: alsa-utils Version: 1.2.12-1 (Debian testing) Severity: minor Tags: patch * What led up to the situation? Checking for defects with test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -ww -b -z < "man page" [Use "groff -e ' $' <file>" to find trailing spaces.] ["test-groff" is a script in the repository for "groff"; is not shipped] (local copy and "troff" slightly changed by me). [The fate of "test-nroff" was decided in groff bug #55941.] * What was the outcome of this action? troff: backtrace: file '<stdin>':3 troff:<stdin>:3: warning: trailing space in the line troff: backtrace: file '<stdin>':87 troff:<stdin>:87: warning: trailing space in the line troff: backtrace: file '<stdin>':91 troff:<stdin>:91: warning: trailing space in the line troff: backtrace: file '<stdin>':95 troff:<stdin>:95: warning: trailing space in the line troff: backtrace: file '<stdin>':99 troff:<stdin>:99: warning: trailing space in the line troff: backtrace: file '<stdin>':103 troff:<stdin>:103: warning: trailing space in the line troff: backtrace: file '<stdin>':107 troff:<stdin>:107: warning: trailing space in the line troff: backtrace: file '<stdin>':111 troff:<stdin>:111: warning: trailing space in the line troff: backtrace: file '<stdin>':114 troff:<stdin>:114: warning: trailing space in the line troff: backtrace: file '<stdin>':115 troff:<stdin>:115: warning: trailing space in the line troff: backtrace: file '<stdin>':118 troff:<stdin>:118: warning: trailing space in the line troff: backtrace: file '<stdin>':121 troff:<stdin>:121: warning: trailing space in the line troff: backtrace: file '<stdin>':131 troff:<stdin>:131: warning: trailing space in the line troff: backtrace: file '<stdin>':215 troff:<stdin>:215: warning: trailing space in the line troff: backtrace: file '<stdin>':225 troff:<stdin>:225: warning: trailing space in the line troff: backtrace: file '<stdin>':258 troff:<stdin>:258: warning: trailing space in the line * What outcome did you expect instead? No output (no warnings). -.- General remarks and further material, if a diff-file exist, are in the attachments. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.11.9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii kmod 33+20240816-2 ii libasound2t64 1.2.12-1+b1 ii libatopology2t64 1.2.12-1+b1 ii libc6 2.40-3 ii libfftw3-single3 3.3.10-1+b3 ii libncursesw6 6.5-2+b1 ii libsamplerate0 0.2.2-4+b2 ii libtinfo6 6.5-2+b1 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: pn dialog <none> -- no debconf information

1 0

[PATCH] ASoC: amd: yc: Fix for enabling DMIC on acp6x via _DSD entry
by Venkata Prasad Potturu 27 Nov '24

27 Nov '24

Add condition check to register ACP PDM sound card by reading _WOV acpi entry. Fixes: 5426f506b584 ("ASoC: amd: Add support for enabling DMIC on acp6x via _DSD") Signed-off-by: Venkata Prasad Potturu <venkataprasad.potturu(a)amd.com> --- sound/soc/amd/yc/acp6x-mach.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/sound/soc/amd/yc/acp6x-mach.c b/sound/soc/amd/yc/acp6x-mach.c index 438865d5e376..c301dac8b979 100644 --- a/sound/soc/amd/yc/acp6x-mach.c +++ b/sound/soc/amd/yc/acp6x-mach.c @@ -523,8 +523,14 @@ static int acp6x_probe(struct platform_device *pdev) struct acp6x_pdm *machine = NULL; struct snd_soc_card *card; struct acpi_device *adev; + acpi_handle handle; + acpi_integer dmic_status; int ret; + bool is_dmic_enable, wov_en; + /* IF WOV entry not found, enable dmic based on AcpDmicConnected entry*/ + is_dmic_enable = false; + wov_en = true; /* check the parent device's firmware node has _DSD or not */ adev = ACPI_COMPANION(pdev->dev.parent); if (adev) { @@ -532,9 +538,19 @@ static int acp6x_probe(struct platform_device *pdev) if (!acpi_dev_get_property(adev, "AcpDmicConnected", ACPI_TYPE_INTEGER, &obj) && obj->integer.value == 1) - platform_set_drvdata(pdev, &acp6x_card); + is_dmic_enable = true; } + handle = ACPI_HANDLE(pdev->dev.parent); + ret = acpi_evaluate_integer(handle, "_WOV", NULL, &dmic_status); + if (!ACPI_FAILURE(ret)) + wov_en = dmic_status; + + if (is_dmic_enable && wov_en) + platform_set_drvdata(pdev, &acp6x_card); + else + return 0; + /* check for any DMI overrides */ dmi_id = dmi_first_match(yc_acp_quirk_table); if (dmi_id) -- 2.39.2

4 5

[BUG] HDA Intel PCH, HDMI , HDA Intel PCH, ALC886 Digital, no IEC958 / HDMI output/passthrough to AVR, partly fixed but HDMI AC3 passthrough
by schorpp 27 Nov '24

27 Nov '24

>>> >>> [BUG] HDA Intel PCH, HDMI , HDA Intel PCH, ALC886 Digital, no IEC958 / HDMI output/passthrough to AVR >>> >>> ALSA versions 1.0.28 >>> >>> Kernel Driver versions 3.12.40 > Partly FIXED in Longterm Stable Kernel 4.19.324 and using HDMI DEV 1 instead of 0. > > 2 CH PCM HDMI to AVR works now but AC3/DTS passthrough still not or is not recognized by AVR or some wrong AES setting but iec958 ALC886 optical toslink AC3/DTS output to AVR works. > > New BUG: No more 5.1 Analog Output on the CM106 USB Box if AC3 stream is selected. No. Sorry, VDR xineliboutput config error, needs speaker setup 5.1 instead of pass through. y tom > > Your ALSA information is located at http://alsa-project.org/db/?f=5ef8b56450583ba8afbcc705afc02228da4a3072 > > y > tom > >>> >>> Hardware: >>> >>> DFI Mainboard MB330-CRM >>> >>> https://www.dfi.com/de/product/index/273#specification >>> >>> Reproducible Always >>> >>> Steps to reproduce and full report: >>> >>> https://www-vdr--portal-de.translate.goog/forum/index.php?thread/136519-gel… >> Output of alsa-info.sh is here >> >> http://alsa-project.org/db/?f=fc4734deddd9a92331692bf94b15cf84b7722cd4 >> >>> >>> Software crosscheck with CM106 USB Soundbox iec958: works OK. >>> >>> Where to start in the drivers source code to fix it? >>> >>> y >>> tom >>> >>>

1 0

alsa-ucm-conf update from 1.2.12 to 1.2.13 causes HDMI/DsiplayPort outputs to disappear
by GitHub issues - opened 27 Nov '24

27 Nov '24

alsa-project/alsa-ucm-conf issue #477 was opened from mwsltn: Basic Info: Linux Distro: Arch Kernel Version: 6.12.1 I have very reliably been using a USB-C connected external monitor that has internal speakers represented by the output device: HDMI / DisplayPort 1 After running a package update this AM all the HDMI/DisplayPort outputs disappeared. First I downgraded the kernel which didn't help, then checked the pacman logs to see what else had changed and the list included the following: ``` [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-ucm-conf (1.2.12-1 -> 1.2.13-1) [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-lib (1.2.12-1 -> 1.2.13-1) [2024-11-26T05:07:01-0600] [ALPM] upgraded alsa-utils (1.2.12-1 -> 1.2.13-1) ``` So I downgrade: ``` [2024-11-26T06:51:22-0600] [PACMAN] Running 'pacman -U file:///var/cache/pacman/pkg/alsa-ucm-conf-1.2.12-1-any.pkg.tar.zst file:///var/cache/pacman/pkg/alsa-lib-1.2.12-1-x86_64.pkg.tar.zst file:///var/cache/pacman/pkg/alsa-utils-1.2.12-1-x86_64.pkg.tar.zst' [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-ucm-conf (1.2.13-1 -> 1.2.12-1) [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-lib (1.2.13-1 -> 1.2.12-1) [2024-11-26T06:51:24-0600] [ALPM] downgraded alsa-utils (1.2.13-1 -> 1.2.12-1) ``` Problem fixed. Please let me know if I can provide any other info. Originally I had opened an issue on the `alsa-lib` project and others are reporting the same: https://github.com/alsa-project/alsa-lib/issues/423 Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/477 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0