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

[PATCH] ASoC: codecs: allow SSM2518 to be selected by the user
by Lucas Stach 30 Jun '21

30 Jun '21

Allow the Analog SSM2518 driver to be enabled without a large bunch of other drivers. Signed-off-by: Lucas Stach <l.stach(a)pengutronix.de> --- sound/soc/codecs/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig index 2a7b3e363069..8f67c400d268 100644 --- a/sound/soc/codecs/Kconfig +++ b/sound/soc/codecs/Kconfig @@ -1316,7 +1316,7 @@ config SND_SOC_SSM2305 high-efficiency mono Class-D audio power amplifiers. config SND_SOC_SSM2518 - tristate + tristate "Analog Devices SSM2518 Class-D Amplifier" depends on I2C config SND_SOC_SSM2602 -- 2.30.2

2 1

Re: [PATCH 1/2] ASoC: rt711: remap buttons
by Mark Brown 30 Jun '21

30 Jun '21

On Thu, Jun 17, 2021 at 01:19:05PM +0000, Shuming [范書銘] wrote: > > > This patch uses the same mapping as the machine driver: > > > BTN_0 : KEY_PLAYPAUSE > > > BTN_1 : KEY_VOICECOMMAND > > > BTN_2 : KEY_VOLUMEUP > > > BTN_3 : KEY_VOLUMEDOWN > > Which machine driver? Can't there be multiple machine drivers, and if > > they're already overriding things why do this? > The rt711 codec is designed in the Intel platform only for now. I'm sure your sales team would be happy to change that! > The machine driver is 'sof_sdw.c' that resides under sound/soc/intel/boards. > It seems Intel uses the same mapping in all other Intel machine drivers. > Please check the commit as below. > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?i… Sure, but if the machine drivers for these platforms already do the right thing why change the CODEC driver? > Hi Sathya, > Do you know why the m/c driver uses this mapping? I'd guess it's just because that's the standard set of headphone buttons that Intel uses for their platforms.

5 6

Warnings while building alsa-gobject
by GitHub issues - opened 29 Jun '21

29 Jun '21

alsa-project/alsa-gobject issue #60 was opened from playaspec: ``` spec@spec-OBSPro:/opt/alsa-gobject-0.2.0/build$ ninja [1/80] Generating alsactl-sigs-marshal_c with a custom command INFO: Reading ../src/ctl/alsactl-sigs-marshal.list... [2/80] Generating alsactl-sigs-marshal_h with a custom command INFO: Reading ../src/ctl/alsactl-sigs-marshal.list... [71/80] Generating ALSACtl-0.0.gir with a custom command g-ir-scanner: link: x86_64-linux-gnu-gcc -pthread -o /opt/alsa-gobject-0.2.0/build/tmp-introspectwlgw8uso/ALSACtl-0.0 /opt/alsa-gobject-0.2.0/build/tmp-introspectwlgw8uso/ALSACtl-0.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/opt/alsa-gobject-0.2.0/build/src/ctl -Wl,-rpath,/opt/alsa-gobject-0.2.0/build/src/ctl -lalsactl -lgobject-2.0 -lglib-2.0 -ludev -lgirepository-1.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 [73/80] Generating ALSATimer-0.0.gir with a custom command g-ir-scanner: link: x86_64-linux-gnu-gcc -pthread -o /opt/alsa-gobject-0.2.0/build/tmp-introspecth2cag8su/ALSATimer-0.0 /opt/alsa-gobject-0.2.0/build/tmp-introspecth2cag8su/ALSATimer-0.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/opt/alsa-gobject-0.2.0/build/src/timer -Wl,-rpath,/opt/alsa-gobject-0.2.0/build/src/timer -lalsatimer -lgobject-2.0 -lglib-2.0 -ludev -lgirepository-1.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 [75/80] Generating ALSARawmidi-0.0.gir with a custom command g-ir-scanner: link: x86_64-linux-gnu-gcc -pthread -o /opt/alsa-gobject-0.2.0/build/tmp-introspectirtcfspf/ALSARawmidi-0.0 /opt/alsa-gobject-0.2.0/build/tmp-introspectirtcfspf/ALSARawmidi-0.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/opt/alsa-gobject-0.2.0/build/src/rawmidi -Wl,-rpath,/opt/alsa-gobject-0.2.0/build/src/rawmidi -lalsarawmidi -lgobject-2.0 -lglib-2.0 -ludev -lgirepository-1.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 [76/80] Generating ALSAHwdep-0.0.gir with a custom command g-ir-scanner: link: x86_64-linux-gnu-gcc -pthread -o /opt/alsa-gobject-0.2.0/build/tmp-introspectbm236ozt/ALSAHwdep-0.0 /opt/alsa-gobject-0.2.0/build/tmp-introspectbm236ozt/ALSAHwdep-0.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/opt/alsa-gobject-0.2.0/build/src/hwdep -Wl,-rpath,/opt/alsa-gobject-0.2.0/build/src/hwdep -lalsahwdep -lgobject-2.0 -lglib-2.0 -ludev -lgirepository-1.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 ../src/hwdep/alsahwdep-enum-types.h:10: Warning: ALSAHwdep: symbol='SNDRV_HWDEP_IFACE_LINE6': Unknown namespace for symbol 'SNDRV_HWDEP_IFACE_LINE6' ../src/hwdep/alsahwdep-enum-types.h:16: Warning: ALSAHwdep: symbol='SNDRV_HWDEP_IFACE_FW_MOTU': Unknown namespace for symbol 'SNDRV_HWDEP_IFACE_FW_MOTU' ../src/hwdep/alsahwdep-enum-types.h:17: Warning: ALSAHwdep: symbol='SNDRV_HWDEP_IFACE_FW_FIREFACE': Unknown namespace for symbol 'SNDRV_HWDEP_IFACE_FW_FIREFACE' [79/80] Generating ALSASeq-0.0.gir with a custom command g-ir-scanner: link: x86_64-linux-gnu-gcc -pthread -o /opt/alsa-gobject-0.2.0/build/tmp-introspectn1rw21o7/ALSASeq-0.0 /opt/alsa-gobject-0.2.0/build/tmp-introspectn1rw21o7/ALSASeq-0.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/opt/alsa-gobject-0.2.0/build/src/timer -Wl,-rpath,/opt/alsa-gobject-0.2.0/build/src/timer -L/opt/alsa-gobject-0.2.0/build/src/seq -Wl,-rpath,/opt/alsa-gobject-0.2.0/build/src/seq -L/opt/alsa-gobject-0.2.0/build/src/timer -Wl,-rpath,/opt/alsa-gobject-0.2.0/build/src/timer -lalsaseq -lalsatimer -lgobject-2.0 -lglib-2.0 -ludev -lgirepository-1.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 [80/80] Generating ALSASeq-0.0.typelib with a custom command ``` Tried both git version and the 0.2.0 tar file. System is Ubuntu Studio 20.04.02 Kernel 5.8.0-59-lowlatency. ALSA: alsa-base 1.0.25+dfsg-0ubuntu5, Pulseaudio 1:13.99.1-1ubuntu3.11, pipewire 0.3.31-3~ubuntu20.04, jack2 1.9.14-0ubuntu2 Running on a Mac Pro 4,1, using a MOTU 828mkII. Perhaps these warnings are inconsequential, but I figured I'd report them since it may affect my hardware. Happy to provide more info and testing. Issue URL : https://github.com/alsa-project/alsa-gobject/issues/60 Repository URL: https://github.com/alsa-project/alsa-gobject

1 0

[PATCH v2] ASoC: remove zte zx dangling kconfig
by Peter Robinson 28 Jun '21

28 Jun '21

In commit dc98f1d we removed the zte zx sound drivers but there was a dangling Kconfig left around for the codec so fix this. Fixes: dc98f1d655ca ("ASoC: remove zte zx drivers") Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com> Cc: Arnd Bergmann <arnd(a)arndb.de> Cc: Mark Brown <broonie(a)kernel.org> --- v2 - fix the Fixes line sound/soc/codecs/Kconfig | 5 ----- 1 file changed, 5 deletions(-) diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig index 1c87b42606c9..e04fa8b5f178 100644 --- a/sound/soc/codecs/Kconfig +++ b/sound/soc/codecs/Kconfig @@ -1739,11 +1739,6 @@ config SND_SOC_ZL38060 which consists of a Digital Signal Processor (DSP), several Digital Audio Interfaces (DAIs), analog outputs, and a block of 14 GPIOs. -config SND_SOC_ZX_AUD96P22 - tristate "ZTE ZX AUD96P22 CODEC" - depends on I2C - select REGMAP_I2C - # Amp config SND_SOC_LM4857 tristate -- 2.31.1

3 2

[PATCH] ASoC: atmel: ATMEL drivers depend on HAS_DMA
by Randy Dunlap 28 Jun '21

28 Jun '21

On a config (such as arch/sh/) which does not set HAS_DMA when MMU is not set, several ATMEL ASoC drivers select symbols that cause kconfig warnings. There is one "depends on HAS_DMA" here but several more are needed to prevent kconfig warnings since 'select' does not recognize any dependencies. Fix the following kconfig warnings: WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_PDC Depends on [n]: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && HAS_DMA [=n] Selected by [m]: - SND_ATMEL_SOC_SSC [=m] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] - SND_ATMEL_SOC_SSC_PDC [=m] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && ATMEL_SSC [=m] WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_SSC_PDC Depends on [n]: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && ATMEL_SSC [=m] && HAS_DMA [=n] Selected by [m]: - SND_AT91_SOC_SAM9G20_WM8731 [=m] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && (ARCH_AT91 || COMPILE_TEST [=y]) && ATMEL_SSC [=m] && SND_SOC_I2C_AND_SPI [=m] WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_SSC Depends on [n]: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && HAS_DMA [=n] Selected by [m]: - SND_ATMEL_SOC_SSC_DMA [=m] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && ATMEL_SSC [=m] WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_SSC_DMA Depends on [n]: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && ATMEL_SSC [=m] && HAS_DMA [=n] Selected by [m]: - SND_ATMEL_SOC_WM8904 [=m] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && (ARCH_AT91 || COMPILE_TEST [=y]) && ATMEL_SSC [=m] && I2C [=m] - SND_AT91_SOC_SAM9X5_WM8731 [=m] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_ATMEL_SOC [=m] && (ARCH_AT91 || COMPILE_TEST [=y]) && ATMEL_SSC [=m] && SND_SOC_I2C_AND_SPI [=m] Fixes: 3951e4aae2ce ("ASoC: atmel-pcm: dma support based on pcm dmaengine") Fixes: 18291410557f ("ASoC: atmel: enable SOC_SSC_PDC and SOC_SSC_DMA in Kconfig") Fixes: 061981ff8cc8 ("ASoC: atmel: properly select dma driver state") Signed-off-by: Randy Dunlap <rdunlap(a)infradead.org> Cc: Codrin Ciubotariu <codrin.ciubotariu(a)microchip.com> Cc: alsa-devel(a)alsa-project.org Cc: Liam Girdwood <lgirdwood(a)gmail.com> Cc: Mark Brown <broonie(a)kernel.org> Cc: Bo Shen <voice.shen(a)atmel.com> Cc: Michał Mirosław <mirq-linux(a)rere.qmqm.pl> Cc: Alexandre Belloni <alexandre.belloni(a)free-electrons.com> --- sound/soc/atmel/Kconfig | 6 ++++++ 1 file changed, 6 insertions(+) --- linux-next-20210528.orig/sound/soc/atmel/Kconfig +++ linux-next-20210528/sound/soc/atmel/Kconfig @@ -19,12 +19,14 @@ config SND_ATMEL_SOC_DMA config SND_ATMEL_SOC_SSC tristate + depends on HAS_DMA select SND_ATMEL_SOC_DMA select SND_ATMEL_SOC_PDC config SND_ATMEL_SOC_SSC_PDC tristate "SoC PCM DAI support for AT91 SSC controller using PDC" depends on ATMEL_SSC + depends on HAS_DMA select SND_ATMEL_SOC_PDC select SND_ATMEL_SOC_SSC help @@ -34,6 +36,7 @@ config SND_ATMEL_SOC_SSC_PDC config SND_ATMEL_SOC_SSC_DMA tristate "SoC PCM DAI support for AT91 SSC controller using DMA" depends on ATMEL_SSC + depends on HAS_DMA select SND_ATMEL_SOC_DMA select SND_ATMEL_SOC_SSC help @@ -44,6 +47,7 @@ config SND_AT91_SOC_SAM9G20_WM8731 tristate "SoC Audio support for WM8731-based At91sam9g20 evaluation board" depends on ARCH_AT91 || COMPILE_TEST depends on ATMEL_SSC && SND_SOC_I2C_AND_SPI + depends on HAS_DMA select SND_ATMEL_SOC_SSC_PDC select SND_SOC_WM8731 help @@ -54,6 +58,7 @@ config SND_ATMEL_SOC_WM8904 tristate "Atmel ASoC driver for boards using WM8904 codec" depends on ARCH_AT91 || COMPILE_TEST depends on ATMEL_SSC && I2C + depends on HAS_DMA select SND_ATMEL_SOC_SSC_DMA select SND_SOC_WM8904 help @@ -64,6 +69,7 @@ config SND_AT91_SOC_SAM9X5_WM8731 tristate "SoC Audio support for WM8731-based at91sam9x5 board" depends on ARCH_AT91 || COMPILE_TEST depends on ATMEL_SSC && SND_SOC_I2C_AND_SPI + depends on HAS_DMA select SND_ATMEL_SOC_SSC_DMA select SND_SOC_WM8731 help

2 4

[PATCH v4 2/2] ASoC: sun50i-dmic: dt-bindings: add DT bindings for DMIC controller
by fengzheng923＠gmail.com 28 Jun '21

28 Jun '21

From: Ban Tao <fengzheng923(a)gmail.com> DT binding documentation for this new ASoC driver. Signed-off-by: Ban Tao <fengzheng923(a)gmail.com> Reviewed-by: Rob Herring <robh(a)kernel.org> --- v1->v2: 1.Fix some build errors. --- v2->v3: 1.Fix some build errors. --- v3->v4: 1.None. --- .../sound/allwinner,sun50i-h6-dmic.yaml | 68 +++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml diff --git a/Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml b/Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml new file mode 100644 index 000000000000..d9107685b78d --- /dev/null +++ b/Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml @@ -0,0 +1,68 @@ +# SPDX-License-Identifier: (GPL-2.0+ OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/sound/allwinner,sun50i-h6-dmic.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Allwinner H6 DMIC Device Tree Bindings + +maintainers: + - Ban Tao <fengzheng923(a)gmail.com> + +properties: + "#sound-dai-cells": + const: 0 + + compatible: + const: allwinner,sun50i-h6-dmic + + reg: + maxItems: 1 + + clocks: + items: + - description: Bus Clock + - description: Module Clock + + clock-names: + items: + - const: bus + - const: mod + + dmas: + items: + - description: RX DMA Channel + + dma-names: + items: + - const: rx + + resets: + maxItems: 1 + +required: + - "#sound-dai-cells" + - compatible + - reg + - clocks + - clock-names + - dmas + - dma-names + - resets + +additionalProperties: false + +examples: + - | + dmic: dmic@5095000 { + #sound-dai-cells = <0>; + compatible = "allwinner,sun50i-h6-dmic"; + reg = <0x05095000 0x400>; + clocks = <&ccu 101>, <&ccu 100>; + clock-names = "bus", "mod"; + dmas = <&dma 7>; + dma-names = "rx"; + resets = <&ccu 42>; + }; + +... -- 2.17.1

2 1

vc4: hdmi: audio: ASoC: error at snd_soc_dai_startup on fef00700.hdmi
by Stefan Wahren 28 Jun '21

28 Jun '21

Hi, yesterday i was testing with Linux 5.13-rc3 on my Raspberry Pi 4 B (multi_v7_defconfig) and i'm getting the following errors during boot: [ 25.947494] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.947512] MAI: soc_pcm_open() failed (-19) [ 25.947883] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.947891] MAI: soc_pcm_open() failed (-19) [ 25.948566] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 25.948577] MAI: soc_pcm_open() failed (-19) [ 26.500049] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.500065] MAI: soc_pcm_open() failed (-19) [ 26.500608] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.500617] MAI: soc_pcm_open() failed (-19) [ 26.502339] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.502353] MAI: soc_pcm_open() failed (-19) [ 26.502569] vc4_hdmi fef00700.hdmi: ASoC: error at snd_soc_dai_startup on fef00700.hdmi: -19 [ 26.502578] MAI: soc_pcm_open() failed (-19) Rootfs: Raspberry Pi OS 32 bit (April 2021) But according to aplay -l both hdmi devices have been registered. Does anyone have seen this, too? Best regards Stefan

2 6

[PATCH alsa-lib] Fix build with --disable-ucm
by Michael Forney 28 Jun '21

28 Jun '21

A recent change introduced a dependency on ucm to several of the other components, but this was not made conditional on whether BUILD_UCM is enabled. Signed-off-by: Michael Forney <mforney(a)mforney.org> --- src/control/control.c | 5 ++++- src/pcm/pcm.c | 5 ++++- src/rawmidi/rawmidi.c | 5 ++++- src/seq/seq.c | 5 ++++- src/timer/timer.c | 5 ++++- 5 files changed, 20 insertions(+), 5 deletions(-) diff --git a/src/control/control.c b/src/control/control.c index 91415b51..ca302df6 100644 --- a/src/control/control.c +++ b/src/control/control.c @@ -1569,11 +1569,14 @@ int snd_ctl_open(snd_ctl_t **ctlp, const char *name, int mode) int err; assert(ctlp && name); +#ifdef BUILD_UCM if (_snd_is_ucm_device(name)) { name = uc_mgr_alibcfg_by_device(&top, name); if (name == NULL) return -ENODEV; - } else { + } else +#endif + { err = snd_config_update_ref(&top); if (err < 0) return err; diff --git a/src/pcm/pcm.c b/src/pcm/pcm.c index 892abf98..67912794 100644 --- a/src/pcm/pcm.c +++ b/src/pcm/pcm.c @@ -2686,11 +2686,14 @@ int snd_pcm_open(snd_pcm_t **pcmp, const char *name, int err; assert(pcmp && name); +#ifdef BUILD_UCM if (_snd_is_ucm_device(name)) { name = uc_mgr_alibcfg_by_device(&top, name); if (name == NULL) return -ENODEV; - } else { + } else +#endif + { err = snd_config_update_ref(&top); if (err < 0) return err; diff --git a/src/rawmidi/rawmidi.c b/src/rawmidi/rawmidi.c index 55f44821..f6a60611 100644 --- a/src/rawmidi/rawmidi.c +++ b/src/rawmidi/rawmidi.c @@ -304,11 +304,14 @@ int snd_rawmidi_open(snd_rawmidi_t **inputp, snd_rawmidi_t **outputp, int err; assert((inputp || outputp) && name); +#ifdef BUILD_UCM if (_snd_is_ucm_device(name)) { name = uc_mgr_alibcfg_by_device(&top, name); if (name == NULL) return -ENODEV; - } else { + } else +#endif + { err = snd_config_update_ref(&top); if (err < 0) return err; diff --git a/src/seq/seq.c b/src/seq/seq.c index f051426f..3330e770 100644 --- a/src/seq/seq.c +++ b/src/seq/seq.c @@ -978,11 +978,14 @@ int snd_seq_open(snd_seq_t **seqp, const char *name, int err; assert(seqp && name); +#if BUILD_UCM if (_snd_is_ucm_device(name)) { name = uc_mgr_alibcfg_by_device(&top, name); if (name == NULL) return -ENODEV; - } else { + } else +#endif + { err = snd_config_update_ref(&top); if (err < 0) return err; diff --git a/src/timer/timer.c b/src/timer/timer.c index 6fc710b9..52400058 100644 --- a/src/timer/timer.c +++ b/src/timer/timer.c @@ -205,11 +205,14 @@ int snd_timer_open(snd_timer_t **timer, const char *name, int mode) int err; assert(timer && name); +#ifdef BUILD_UCM if (_snd_is_ucm_device(name)) { name = uc_mgr_alibcfg_by_device(&top, name); if (name == NULL) return -ENODEV; - } else { + } else +#endif + { err = snd_config_update_ref(&top); if (err < 0) return err; -- 2.32.0

2 1

Dell platform adding ucm2 conf with generic mic-mute LEDs feature
by GitHub issues - opened 28 Jun '21

28 Jun '21

alsa-project/alsa-ucm-conf issue #105 was opened from GoPerry: As the post-patch did, I would need to add one patch for the dell platform which has enabled the generic mic mute feature. But I did not see the below paths. /sys/class/sound/ctl-led/speaker /sys/class/sound/ctl-led/mic https://www.spinics.net/lists/alsa-devel/msg125821.html Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/105 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Starting with 1.2.5 alsactl tries to initialize UCM even if it is not supported
by GitHub issues - edited 27 Jun '21

27 Jun '21

alsa-project/alsa-utils issue #101 was edited from nmeum: Starting with alsa-utils 1.2.5 I observed the following warning on my machine when running `alsactl restore 0`, which I didn't receive prevously with alsa-utils 1.2.4: ``` $ alsactl -E 'HOME=/var/run/alsasound' -I -f /var/lib/alsa/asound.state restore 0 alsa-lib parser.c:2372:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'. alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 ``` The error message tells me that alsa-utils 1.2.5 now tries to initialize UCM by default which doesn't work since I don't have [alsa-ucm-conf](https://github.com/alsa-project/alsa-ucm-conf) installed. After installing alsa-ucm-conf, the error message looks as follows: ``` $ alsactl -E 'HOME=/var/run/alsasound' -I -f /var/lib/alsa/asound.state restore 0 alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0xf2530000 irq 35) alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6 ``` >From reading the alsactl man page, it seems to me that UCM should only be initialized by default if it is available. Since alsactl 1.2.4 did not attempt to initialize UCM on my machine, this seems to be a regression introduced in alsactl 1.2.5. If I disable UCM explicitly using `alsactl -U`, everything works as expected. Similarly, downgrading to alsactl 1.2.4 again also resolves the issue. I am not familiar at all with alsa internals but if desired, I can check with `git-bisect(1)` which commit between `v1.2.4..v1.2.5` introduced this regression. Issue URL : https://github.com/alsa-project/alsa-utils/issues/101 Repository URL: https://github.com/alsa-project/alsa-utils

1 0