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

[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

alsactl.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 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>':93 troff:<stdin>:93: warning: trailing space in the line troff: backtrace: file '<stdin>':224 troff:<stdin>:224: 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

alsabat.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>':175 troff:<stdin>:175: 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

RE: Set pcbeep to default value
by Kailang 26 Nov '24

26 Nov '24

Sorry! Attach again. Add ALSA: hda/realtek: to Title. > -----Original Message----- > From: Kailang > Sent: Tuesday, November 26, 2024 10:36 AM > To: 'Takashi Iwai' <tiwai(a)suse.de> > Cc: (alsa-devel(a)alsa-project.org) <alsa-devel(a)alsa-project.org>; > 'linux-sound(a)vger.kernel.org' <linux-sound(a)vger.kernel.org> > Subject: RE: Set pcbeep to default value > > OK. > > > -----Original Message----- > > From: Takashi Iwai <tiwai(a)suse.de> > > Sent: Monday, November 25, 2024 10:45 PM > > To: Kailang <kailang(a)realtek.com> > > Cc: Takashi Iwai <tiwai(a)suse.de> > > Subject: Re: Set pcbeep to default value > > > > > > External mail. > > > > > > > > On Mon, 25 Nov 2024 03:00:26 +0100, > > Kailang wrote: > > > > > > > > > > > > > -----Original Message----- > > > > From: Takashi Iwai <tiwai(a)suse.de> > > > > Sent: Friday, November 22, 2024 5:34 PM > > > > To: Kailang <kailang(a)realtek.com> > > > > Cc: (alsa-devel(a)alsa-project.org) <alsa-devel(a)alsa-project.org> > > > > Subject: Re: Set pcbeep to default value > > > > > > > > > > > > External mail. > > > > > > > > > > > > > > > > On Fri, 22 Nov 2024 08:29:56 +0100, Kailang wrote: > > > > > > > > > > Hi Takashi, > > > > > > > > > > Attach patch will set pcbeep to default value for ALC274. > > > > > > > > Could you resubmit with your Signed-off-by tag? > > > > > > Sorry! Attach again. > > > > You seem to have dropped Cc to alsa-devel ML. > > Also, nowadays we use linux-sound(a)vger.kernel.org for the main ML for > > kernel patches. Care to resubmit to there? > > > > > > thanks, > > > > Takashi

2 1

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

26 Nov '24

alsa-project/alsa-lib issue #423 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. Issue URL : https://github.com/alsa-project/alsa-lib/issues/423 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

kernel snd seq bugs: SND_SEQ_EVENT_CLIENT_CHANGE & SND_SEQ_EVENT_PORT_CHANGE
by Mark Lentczner 26 Nov '24

26 Nov '24

I'm the author of amidiminder - a utility that keeps track of desired connections between ALSA Seq (MIDI) ports. I've found a bug in the kernel part of the ALSA Sequencer, and am not sure where or how to report it. Summary: The events: * SND_SEQ_EVENT_CLIENT_CHANGE is never sent * SND_SEQ_EVENT_PORT_CHANGE is not sent on common port changes (name and port info) I have a lot of detail on these bugs, what other software causes them to be a problem (PureData), and where the missing code in the kernel sound/core/seq files is. Before I dump all the details in this forum.... where is the right place for me to report and/or discuss this? - Mark

2 3

Build failures with GCC 15 (-std=gnu23)
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-tools issue #25 was edited from kostadinsh: Some of the programs in alsa-tools fail to build with upcoming GCC 15 which uses `-std=gnu23` by default. This can be reproduced on older GCC and Clang versions by adding `-std=gnu23` to CFLAGS. Downstream Gentoo bug report: https://bugs.gentoo.org/943946 hdajackretask: ``` apply-changes.c:358:10: error: conflicting types for ‘reset_changes_boot’; have ‘gboolean(GError **)’ {aka ‘int(struct _GError **)’} 358 | gboolean reset_changes_boot(GError** err) | ^~~~~~~~~~~~~~~~~~ In file included from apply-changes.c:12: apply-changes.h:12:10: note: previous declaration of ‘reset_changes_boot’ with type ‘gboolean(void)’ {aka ‘int(void)’} 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ main-gtk.c: In function ‘reset_boot_clicked’: main-gtk.c:375:5: error: too many arguments to function ‘reset_changes_boot’ 375 | reset_changes_boot(&err); | ^~~~~~~~~~~~~~~~~~ In file included from main-gtk.c:11: apply-changes.h:12:10: note: declared here 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ ``` envy24control: ``` new_process.c: In function ‘new_process’: new_process.c:67:18: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 67 | int_stat = signal(SIGINT, SIG_IGN); | ^ new_process.c:68:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 68 | quit_stat = signal(SIGQUIT, SIG_IGN); | ^ new_process.c:69:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 69 | usr2_stat = signal(SIGUSR2, SIG_IGN); | ^ new_process.c:81:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 81 | signal(SIGINT, int_stat); | ^~~~~~~~ | | | void (*)(void) In file included from envy24control.h:4: /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:82:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 82 | signal(SIGQUIT, quit_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:83:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 83 | signal(SIGUSR2, usr2_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ ``` Issue URL : https://github.com/alsa-project/alsa-tools/issues/25 Repository URL: https://github.com/alsa-project/alsa-tools

1 0

Build failures with GCC 15 (-std=gnu23)
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-tools issue #25 was opened from kostadinsh: Some of the programs in alsa-tools fail to build with upcoming GCC 15 which uses `-std=gnu23` by default. This can be reproduced on older GCC and Clang versions by adding `-std=gnu23` to CFLAGS. Downstream Gentoo bug report: https://bugs.gentoo.org/943946 hdajackretask: ``` main-gtk.c: In function ‘reset_boot_clicked’: main-gtk.c:375:5: error: too many arguments to function ‘reset_changes_boot’ 375 | reset_changes_boot(&err); | ^~~~~~~~~~~~~~~~~~ In file included from main-gtk.c:11: apply-changes.h:12:10: note: declared here 12 | gboolean reset_changes_boot(); | ^~~~~~~~~~~~~~~~~~ ``` envy24control: ``` new_process.c: In function ‘new_process’: new_process.c:67:18: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 67 | int_stat = signal(SIGINT, SIG_IGN); | ^ new_process.c:68:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 68 | quit_stat = signal(SIGQUIT, SIG_IGN); | ^ new_process.c:69:19: error: assignment to ‘void (*)(void)’ from incompatible pointer type ‘__sighandler_t’ {aka ‘void (*)(int)’} [-Wincompatible-pointer-types] 69 | usr2_stat = signal(SIGUSR2, SIG_IGN); | ^ new_process.c:81:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 81 | signal(SIGINT, int_stat); | ^~~~~~~~ | | | void (*)(void) In file included from envy24control.h:4: /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:82:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 82 | signal(SIGQUIT, quit_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ new_process.c:83:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 83 | signal(SIGUSR2, usr2_stat); | ^~~~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ ``` Issue URL : https://github.com/alsa-project/alsa-tools/issues/25 Repository URL: https://github.com/alsa-project/alsa-tools

1 0

No built-in microphone in Thinkpad X1 Carbon (Gen 12) after update to v1.2.13
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #476 was opened from iyanmv: I think the title is self-explanatory. After updating from v1.2.12 to v1.2.13 in Arch Linux, the built-in microphone on my laptop is not working. Downgrading to previous versions fixes the issue. In addition, I also noticed that when attached to an external monitor using a docking station, the speakers of the monitor are not listed as before, and only the laptop's built-in speaker appears. I'm running linux 6.12.1 and KDE Plasma 6.2.3. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/476 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

how do I create configure a ucm2 conf file for my card just like an acp file
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #475 was opened from beh-10257: 1_ how do I know if my card is using acp or ucm profile 2_ can ucm config file be availble in user directories 3_ how do i test a ucm profile 4_ if my card is using ucm is there a way to cooverride that file 5_ for more context https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4421 6_ as a tldr I want to take advanatage of indep_hp=yes (IDK why this is not enabled by default its a great feature compared to other platforms after all) either way I want to make hw:0,0 as speaker and hw:0,2 as headphones can a ucm profile replace the indep_hp hint and udev rule and just porceed to seperate them directly also indep_hp seperates speaker and headphones output is there a way to seperate internal mic and headphone speaker also is there a way to put priority for headphones when the jack port is actually put or even disable it entirely and just default back to speaker automatically thats all thanks thats all and thanks further editing will be filled once I have more questions and thanks Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/475 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

ALC225 update depop procedure
by Kailang 26 Nov '24

26 Nov '24

Hi Takashi, ALC225 update depop procedure. Many Thanks. BR, Kailang

2 1

Enable speaker pins for Medion E15443 platform
by Kailang 26 Nov '24

26 Nov '24

Hi Takashi, Attach was fixed speaker no sound issue. BR, Kailang

2 1

Device selection regression in 1.2.13 for LNL
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was edited from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. According to `aplay -l`, the audio card is sofhdadsp. Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Device selection regression in 1.2.13 for LNL
by GitHub issues - edited 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was edited from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. According to `aplay -l`, the audio card is sofhdadsp . Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Device selection regression in 1.2.13 for LNL
by GitHub issues - opened 26 Nov '24

26 Nov '24

alsa-project/alsa-ucm-conf issue #474 was opened from CarelessCaution: On Intel Lunar Lake, there seems to be a regression in alsa-ucm-conf that affects device selection in KDE Plasma and probably in other software. In 1.2.12, there are the options Play HiFi Quality Music and Pro Audio for both input and output. However, when upgrading to 1.2.13, there is only the option for Pro Audio. This problem is immediately remedied by downgrading just the alsa-ucm-conf package on Arch Linux. Before (1.2.12): ![before](https://github.com/user-attachments/assets/c7fa81e0-97f1-45ae-a14e-8549f85cdd27) After (1.2.13): ![after](https://github.com/user-attachments/assets/5867886b-6686-4265-ad68-50c7f53e1a47) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/474 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

RE: Set pcbeep to default value
by Kailang 26 Nov '24

26 Nov '24

OK. > -----Original Message----- > From: Takashi Iwai <tiwai(a)suse.de> > Sent: Monday, November 25, 2024 10:45 PM > To: Kailang <kailang(a)realtek.com> > Cc: Takashi Iwai <tiwai(a)suse.de> > Subject: Re: Set pcbeep to default value > > > External mail. > > > > On Mon, 25 Nov 2024 03:00:26 +0100, > Kailang wrote: > > > > > > > > > -----Original Message----- > > > From: Takashi Iwai <tiwai(a)suse.de> > > > Sent: Friday, November 22, 2024 5:34 PM > > > To: Kailang <kailang(a)realtek.com> > > > Cc: (alsa-devel(a)alsa-project.org) <alsa-devel(a)alsa-project.org> > > > Subject: Re: Set pcbeep to default value > > > > > > > > > External mail. > > > > > > > > > > > > On Fri, 22 Nov 2024 08:29:56 +0100, > > > Kailang wrote: > > > > > > > > Hi Takashi, > > > > > > > > Attach patch will set pcbeep to default value for ALC274. > > > > > > Could you resubmit with your Signed-off-by tag? > > > > Sorry! Attach again. > > You seem to have dropped Cc to alsa-devel ML. > Also, nowadays we use linux-sound(a)vger.kernel.org for the main ML for kernel > patches. Care to resubmit to there? > > > thanks, > > Takashi

1 0

GoXLR not working in 1.2.13
by GitHub issues - opened 25 Nov '24

25 Nov '24

alsa-project/alsa-ucm-conf issue #473 was opened from AruAki: GoXLR not splitting into multiple channels. `alsaucm -c hw:1 dump text` returns ``` ALSA lib parser.c:270:(parse_syntax_field) Incompatible syntax 7 in USB-Audio.conf ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -22 alsaucm: error failed to open sound card hw:1: Invalid argument ``` Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/473 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[RFC PATCH 0/2] Add support for stacked and parallel memories
by Amit Kumar Mahapatra 25 Nov '24

25 Nov '24

Hello Everyone, Following an email discussion with Miquel regarding the binding changes and overall architecture for implementing support for stacked and parallel memories, I’m sharing this RFC to initiate a discussion on the proposed updates to current bindings and to finalize the implementation architecture. Before diving into the main topic, here is some background on stacked and parallel memories. The AMD QSPI controller supports two advanced connection modes(Stacked and Parallel) which allow the controller to treat two different flashes as one storage. Stacked: Flashes share the same SPI bus, but different CS line, controller driver asserts the CS of the flash to which it needs to communicate. Stacked mode is a software abstraction rather than a controller feature or capability. At any given time, the controller communicates with one of the two connected flash devices, as determined by the requested address and data length. If an operation starts on one flash and ends on the other, the core needs to split it into two separate operations and adjust the data length accordingly. Parallel(Multi-CS): Both the flashes have their separate SPI bus, CS of both the flashes will be asserted/de-asserted at the same time. In this mode data will be split across both the flashes by enabling the STRIPE setting in the controller. Parallel mode is a controller feature where if the STRIPE bit is set then the controller internally handles the data split during data write to the flashes and while reading data from the flash the controller internally merges data from both the flashes before writing to the controller FIFO. If STRIPE is not enabled, then same data will be sent to both the devices. In parallel mode both the flashes should be identical. For more information on the modes please feel free to go through the controller flash interface below [1]. Mirochip QSPI controller[2] also supports "Dual Parallel 8-bit IO mode", but they call it "Twin Quad Mode". Initially in [3] [4] [5] Miquel had tried to extend MTD-CONCAT driver to support Stacked mode, but the bindings were not accepted. So, the MTD-CONCAT approach was dropped and the DT bindings that got accepted [6] [7] [8] that describes the two flash devices as being one. SPI core changes to support the above bindings were added [9]. While adding the support in SPI-NOR Tudor provided additional feedback, leading to a discussion on updating the current stacked and parallel DT bindings. Proposed Solution: The solution has two parts: 1. Update MTD-CONCAT Update MTD-CONCAT to create virtual concatinated mtd devices as defined in the device tree. 2. Add a New Layer Add a new layer between the SPI-NOR and MTD layers to support stacked and parallel configurations. This new layer will be part of spi-nor, located in mtd/spi-nor/, can be included/excluded via Kconfig, will be maintained by AMD and will: - During probing, store information from all connected flashes in stacked or parallel mode and present them as a single device to the MTD layer. - Register callbacks and manage MTD device registration within the new layer instead of spi-nor/core.c. - Make minimal changes in spi-nor/core.c, as stacked and parallel handling will be managed by the new layer on top of SPI-NOR. - Handle odd byte count requests from the MTD layer during flash operations in parallel mode. [1] https://docs.amd.com/r/en-US/am011-versal-acap-trm/QSPI-Flash-Device-Interf… [2] https://ww1.microchip.com/downloads/aemDocuments/documents/MPU32/ProductDoc… [3] https://lore.kernel.org/all/20191113171505.26128-4-miquel.raynal@bootlin.co… [4] https://lore.kernel.org/all/20191127105522.31445-5-miquel.raynal@bootlin.co… [5]https://lore.kernel.org/all/20211112152411.818321-1-miquel.raynal@bootlin… [6] https://github.com/torvalds/linux/commit/f89504300e94524d5d5846ff8b728592ac… [7] https://github.com/torvalds/linux/commit/eba5368503b4291db7819512600fa014ea… [8] https://github.com/torvalds/linux/commit/e2edd1b64f1c79e8abda365149ed62a2a9… [9]https://github.com/torvalds/linux/commit/4d8ff6b0991d5e86b17b235fc46ec62e… Thanks, Amit Amit Kumar Mahapatra (2): dt-bindings: mtd: Add bindings for describing concatinated MTD devices dt-bindings: spi: Update stacked and parallel bindings .../mtd/partitions/fixed-partitions.yaml | 18 +++++++++++++++ .../bindings/mtd/partitions/partitions.yaml | 6 +++++ .../bindings/spi/spi-controller.yaml | 23 +++++++++++++++++-- .../bindings/spi/spi-peripheral-props.yaml | 9 +++----- 4 files changed, 48 insertions(+), 8 deletions(-) -- 2.34.1

6 15

ABI break in 1.2.12 -> 1.2.13
by GitHub issues - edited 25 Nov '24

25 Nov '24

alsa-project/alsa-lib issue #422 was edited from bbhtt: This seems a bit unusual for a patch version bump. Any idea what this is about? Thanks! ``` ┌───────────────────────────┐ │ ABI Break: libasound.so.2 │ └───────────────────────────┘ Functions changes summary: 1 Removed, 3 Changed (250 filtered out), 35 Added functions Variables changes summary: 0 Removed, 0 Changed, 0 Added variable 1 Removed function: [D] 'function void snd_ump_block_info_set_block_id(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_block_id@@ALSA_1.2.10} 35 Added functions: [A] 'function const unsigned char* snd_pcm_hw_params_get_sync(const snd_pcm_hw_params_t*)' {snd_pcm_hw_params_get_sync@@ALSA_1.2.13} [A] 'function int snd_seq_create_ump_block(snd_seq_t*, int, const snd_ump_block_info_t*)' {snd_seq_create_ump_block@@ALSA_1.2.13} [A] 'function int snd_seq_create_ump_endpoint(snd_seq_t*, const snd_ump_endpoint_info_t*, unsigned int)' {snd_seq_create_ump_endpoint@@ALSA_1.2.13} [A] 'function int snd_seq_has_queue_tempo_base(snd_seq_t*)' {snd_seq_has_queue_tempo_base@@ALSA_0.9} [A] 'function int snd_seq_port_info_get_ump_is_midi1(const snd_seq_port_info_t*)' {snd_seq_port_info_get_ump_is_midi1@@ALSA_1.2.13} [A] 'function void snd_seq_port_info_set_ump_is_midi1(snd_seq_port_info_t*, int)' {snd_seq_port_info_set_ump_is_midi1@@ALSA_1.2.13} [A] 'function unsigned int snd_seq_queue_tempo_get_tempo_base(const snd_seq_queue_tempo_t*)' {snd_seq_queue_tempo_get_tempo_base@@ALSA_1.2.13} [A] 'function void snd_seq_queue_tempo_set_tempo_base(snd_seq_queue_tempo_t*, unsigned int)' {snd_seq_queue_tempo_set_tempo_base@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_clear(snd_ump_block_info_t*)' {snd_ump_block_info_clear@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_active(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_active@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_card(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_card@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_device(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_device@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_direction(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_direction@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_first_group(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_first_group@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_flags(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_flags@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_midi_ci_version(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_midi_ci_version@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_name(snd_ump_block_info_t*, const char*)' {snd_ump_block_info_set_name@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_num_groups(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_num_groups@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_sysex8_streams(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_sysex8_streams@@ALSA_1.2.13} [A] 'function void snd_ump_block_info_set_ui_hint(snd_ump_block_info_t*, unsigned int)' {snd_ump_block_info_set_ui_hint@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_clear(snd_ump_endpoint_info_t*)' {snd_ump_endpoint_info_clear@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_card(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_card@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_device(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_device@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_family_id(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_family_id@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_flags(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_flags@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_manufacturer_id(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_manufacturer_id@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_model_id(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_model_id@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_name(snd_ump_endpoint_info_t*, const char*)' {snd_ump_endpoint_info_set_name@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_num_blocks(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_num_blocks@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_product_id(snd_ump_endpoint_info_t*, const char*)' {snd_ump_endpoint_info_set_product_id@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_protocol(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_protocol@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_protocol_caps(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_protocol_caps@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_sw_revision(snd_ump_endpoint_info_t*, const unsigned char*)' {snd_ump_endpoint_info_set_sw_revision@@ALSA_1.2.13} [A] 'function void snd_ump_endpoint_info_set_version(snd_ump_endpoint_info_t*, unsigned int)' {snd_ump_endpoint_info_set_version@@ALSA_1.2.13} [A] 'function int snd_ump_packet_length(unsigned int)' {snd_ump_packet_length@@ALSA_1.2.13} 3 functions with some indirect sub-type change: [C] 'function int __old_snd_pcm_hw_params_get_access(const snd_pcm_hw_params_t*)' at pcm.c:8062:1 has some indirect sub-type changes: Please note that the exported symbol of this function is snd_pcm_hw_params_get_access(a)ALSA_0.9 parameter 1 of type 'const snd_pcm_hw_params_t*' has sub-type changes: in pointed to type 'const snd_pcm_hw_params_t': in unqualified underlying type 'typedef snd_pcm_hw_params_t' at pcm.h:64:1: underlying type 'struct snd_pcm_hw_params' at asound.h:414:1 changed: type size hasn't changed 1 data member insertion: 'unsigned char sync[16]', at offset 4352 (in bits) at asound.h:421:1 1 data member change: type of 'unsigned char reserved[64]' changed: type name changed from 'unsigned char[64]' to 'unsigned char[48]' array type size changed from 512 to 384 array type subrange 1 changed length from 64 to 48 array subrange changed: upper bound of '<anonymous range>[48]' change from '63' to '47' and offset changed from 4352 to 4480 (in bits) (by +128 bits) [C] 'function int snd_ctl_pcm_info(snd_ctl_t*, snd_pcm_info_t*)' at control.c:1219:1 has some indirect sub-type changes: parameter 2 of type 'snd_pcm_info_t*' has sub-type changes: in pointed to type 'typedef snd_pcm_info_t' at pcm.h:48:1: underlying type 'struct snd_pcm_info' at asound.h:345:1 changed: type size hasn't changed 1 data member change: type of 'snd_pcm_sync_id sync' changed: entity changed from 'union snd_pcm_sync_id' to 'unsigned char[16]' and name of 'snd_pcm_info::sync' changed to 'snd_pcm_info::pad1' at asound.h:349:1 [C] 'function int snd_seq_get_queue_tempo(snd_seq_t*, int, snd_seq_queue_tempo_t*)' at seq.c:3880:1 has some indirect sub-type changes: parameter 3 of type 'snd_seq_queue_tempo_t*' has sub-type changes: in pointed to type 'typedef snd_seq_queue_tempo_t' at seq.h:441:1: underlying type 'struct snd_seq_queue_tempo' at asequencer.h:540:1 changed: type size hasn't changed 1 data member insertion: 'unsigned short int tempo_base', at offset 160 (in bits) at asequencer.h:532:1 1 data member change: type of 'char reserved[24]' changed: type name changed from 'char[24]' to 'char[22]' array type size changed from 192 to 176 array type subrange 1 changed length from 24 to 22 array subrange changed: upper bound of '<anonymous range>[22]' change from '23' to '21' and offset changed from 160 to 176 (in bits) (by +16 bits) ``` Issue URL : https://github.com/alsa-project/alsa-lib/issues/422 Repository URL: https://github.com/alsa-project/alsa-lib

1 0