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

envy24control: fix spdif output settings
by GitHub pull_request - opened 23 Mar '25

23 Mar '25

alsa-project/alsa-tools pull request #28 was opened from andreas56: The S/PDIF Output Settings in envy24control had some bugs: wrong bits were set when user changed "Stream" under "Professional" or any of the the settings under "Consumer". Request URL : https://github.com/alsa-project/alsa-tools/pull/28 Patch URL : https://github.com/alsa-project/alsa-tools/pull/28.patch Repository URL: https://github.com/alsa-project/alsa-tools

1 0

[Regression] v1.2.13 broke my laptop's headphone microphone
by GitHub issues - opened 22 Mar '25

22 Mar '25

alsa-project/alsa-ucm-conf issue #530 was opened from vixalien: Hello everyone! I have a HP ProBook 440 G8 Notebook PC, and sound and microphones were working correctly on v1.2.12, but now the microphone is not working after upgrading to v1.2.13. Here's my system details: ``` OS: Alpine Linux edge x86_64 Host: HP ProBook 440 G8 Notebook PC Kernel: Linux 6.13.7-0-edge ``` ``` $ arecord -l **** List of CAPTURE Hardware Devices **** card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ``` The `arecord` commands only works when I set the device to 0,6 and 0,7 ``` arecord --duration=5 --format=dat --device=hw:0,0 test-mic.wav # does not work, empty audio arecord --duration=5 --format=dat --device=hw:0,6 test-mic.wav # works arecord --duration=5 --format=dat --device=hw:0,7 test-mic.wav # works ``` On v1.2.12, pipewire is automatically configured to use `0,6`, but on v1.12.13, it seems like it's configured to use `0,0` which causes that audio does not work. I'm sorry this is my first issue report. I'm happy to provie more details if necessary. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/530 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

sof-soundwire: rt1318: add playback control switch
by GitHub pull_request - edited 22 Mar '25

22 Mar '25

alsa-project/alsa-ucm-conf pull request #525 was edited from shumingfan: rt1318: add playback control switch [v2] This patch defines a remapped one 'rt1318 DAC Playback Switch' whether the cases are in one amp or two amps. Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/525 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/525.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

arecord --max-file-time behavior
by GitHub issues - opened 22 Mar '25

22 Mar '25

alsa-project/alsa-utils issue #296 was opened from thk686: I do environmental sound recordings where arecord runs for months to years with --max-file-time set to something like 15 minutes. It is very nice to have this feature, yet there is one aspect that is problematic. It is not simple to know which file is currently being written. One can time stamp the file names and ignore the most recent, which is probably the simplest. Nonetheless, I wonder if it could be the case that the current write file could be named something else, such as the file name but preceded by a . or other indicator, and have it renamed to its intended name once it is closed and arecord has moved on to another file. Issue URL : https://github.com/alsa-project/alsa-utils/issues/296 Repository URL: https://github.com/alsa-project/alsa-utils

1 0

[PATCH 6.1] ALSA: control: Avoid WARN() for symlink errors
by Alexey Nepomnyashih 21 Mar '25

21 Mar '25

From: Takashi Iwai <tiwai(a)suse.de> commit b2e538a9827dd04ab5273bf4be8eb2edb84357b0 upstream. Using WARN() for showing the error of symlink creations don't give more information than telling that something goes wrong, since the usual code path is a lregister callback from each control element creation. More badly, the use of WARN() rather confuses fuzzer as if it were serious issues. This patch downgrades the warning messages to use the normal dev_err() instead of WARN(). For making it clearer, add the function name to the prefix, too. Fixes: a135dfb5de15 ("ALSA: led control - add sysfs kcontrol LED marking layer") Reported-by: syzbot+4e7919b09c67ffd198ae(a)syzkaller.appspotmail.com Closes: https://lore.kernel.org/675664c7.050a0220.a30f1.018c.GAE@google.com Link: https://patch.msgid.link/20241209095614.4273-1-tiwai@suse.de Signed-off-by: Takashi Iwai <tiwai(a)suse.de> [ Alexey Nepomnyashih: changed &card->ctl_dev->kobj to &card->ctl_dev.kobj. ] Signed-off-by: Alexey Nepomnyashih <sdl(a)nppct.ru> --- sound/core/control_led.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/sound/core/control_led.c b/sound/core/control_led.c index 3cadd40100f3..6d81a6a59f29 100644 --- a/sound/core/control_led.c +++ b/sound/core/control_led.c @@ -688,10 +688,16 @@ static void snd_ctl_led_sysfs_add(struct snd_card *card) goto cerr; led->cards[card->number] = led_card; snprintf(link_name, sizeof(link_name), "led-%s", led->name); - WARN(sysfs_create_link(&card->ctl_dev.kobj, &led_card->dev.kobj, link_name), - "can't create symlink to controlC%i device\n", card->number); - WARN(sysfs_create_link(&led_card->dev.kobj, &card->card_dev.kobj, "card"), - "can't create symlink to card%i\n", card->number); + if (sysfs_create_link(&card->ctl_dev.kobj, &led_card->dev.kobj, + link_name)) + dev_err(card->dev, + "%s: can't create symlink to controlC%i device\n", + __func__, card->number); + if (sysfs_create_link(&led_card->dev.kobj, &card->card_dev.kobj, + "card")) + dev_err(card->dev, + "%s: can't create symlink to card%i\n", + __func__, card->number); continue; cerr: -- 2.43.0

1 0

[PATCH] ASoC: amd: yc: update quirk data for new Lenovo model
by Syed Saba Kareem 21 Mar '25

21 Mar '25

From: Syed Saba kareem <syed.sabakareem(a)amd.com> Update Quirk data for new Lenovo model 83J2 for YC platform. Signed-off-by: Syed Saba kareem <syed.sabakareem(a)amd.com> --- sound/soc/amd/yc/acp6x-mach.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/sound/soc/amd/yc/acp6x-mach.c b/sound/soc/amd/yc/acp6x-mach.c index bd3808f98ec9..e632f16c9102 100644 --- a/sound/soc/amd/yc/acp6x-mach.c +++ b/sound/soc/amd/yc/acp6x-mach.c @@ -339,6 +339,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = { DMI_MATCH(DMI_PRODUCT_NAME, "83Q3"), } }, + { + .driver_data = &acp6x_card, + .matches = { + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"), + DMI_MATCH(DMI_PRODUCT_NAME, "83J2"), + } + }, { .driver_data = &acp6x_card, .matches = { -- 2.43.0

3 2

[GIT PULL] ASoC fixes for v6.14-rc7
by Mark Brown 21 Mar '25

21 Mar '25

The following changes since commit 658fb7fe8e7f4014ea17a4da0e0c1d9bc319fa35: ASoC: cs42l43: convert to SYSTEM_SLEEP_PM_OPS (2025-03-12 16:12:24 +0000) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v6.14-rc7 for you to fetch changes up to 45ff65e30deb919604e68faed156ad96ce7474d9: ASoC: ti: j721e-evm: Fix clock configuration for ti,j7200-cpb-audio compatible (2025-03-18 12:27:34 +0000) ---------------------------------------------------------------- ASoC: Fixes for v6.14 A couple of small fixes, plus some new device IDs - nothing super urgent here. ---------------------------------------------------------------- Frank Li (1): ASoC: dt-bindings: fsl,sai: Add i.MX94 support Jayesh Choudhary (1): ASoC: ti: j721e-evm: Fix clock configuration for ti,j7200-cpb-audio compatible Kuninori Morimoto (1): ASoC: simple-card-utils: Don't use __free(device_node) at graph_util_parse_dai() keenplify (1): ASoC: amd: Add DMI quirk for ACP6X mic support Documentation/devicetree/bindings/sound/fsl,sai.yaml | 4 ++++ sound/soc/amd/yc/acp6x-mach.c | 7 +++++++ sound/soc/generic/simple-card-utils.c | 7 +++++-- sound/soc/ti/j721e-evm.c | 2 ++ 4 files changed, 18 insertions(+), 2 deletions(-)

2 1

[tiwai-sound:for-next 8/18] ld: sound/pci/oxygen/oxygen.o:undefined reference to `oxygen_pci_pm'
by kernel test robot 21 Mar '25

21 Mar '25

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next head: ee3d1f09e04643b1b48bd894de1de3c600a01c05 commit: 5ea0a2206b58356779cc686630b6548a3402991c [8/18] ALSA: oxygen: Convert to EXPORT_SIMPLE_DEV_PM_OPS() config: i386-randconfig-061-20250320 (https://download.01.org/0day-ci/archive/20250321/202503211242.zaTMusOT-lkp@…) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250321/202503211242.zaTMusOT-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/202503211242.zaTMusOT-lkp@intel.com/ Note: the tiwai-sound/for-next HEAD ee3d1f09e04643b1b48bd894de1de3c600a01c05 builds fine. It only hurts bisectability. All errors (new ones prefixed by >>): >> ld: sound/pci/oxygen/oxygen.o:(.data+0x454): undefined reference to `oxygen_pci_pm' >> ld: sound/pci/oxygen/virtuoso.o:(.data+0xf4): undefined reference to `oxygen_pci_pm' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[tiwai-sound:for-next 8/17] ld: vmlinux.o:undefined reference to `oxygen_pci_pm'
by kernel test robot 20 Mar '25

20 Mar '25

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next head: 765fee28fe0e7d6a5ff8f2eeb7990b7d3ad20825 commit: 5ea0a2206b58356779cc686630b6548a3402991c [8/17] ALSA: oxygen: Convert to EXPORT_SIMPLE_DEV_PM_OPS() config: x86_64-buildonly-randconfig-002-20250320 (https://download.01.org/0day-ci/archive/20250320/202503201853.7kB0BPRw-lkp@…) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250320/202503201853.7kB0BPRw-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/202503201853.7kB0BPRw-lkp@intel.com/ All errors (new ones prefixed by >>): >> ld: vmlinux.o:(.data+0x57d120): undefined reference to `oxygen_pci_pm' ld: vmlinux.o:(.data+0x57d620): undefined reference to `oxygen_pci_pm' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

Fiio K7 Pro USB DAC no Alsamixer Volume Level
by GitHub issues - opened 19 Mar '25

19 Mar '25

alsa-project/alsa-lib issue #444 was opened from Starfoxfs: Hi, i cant set any Volume Level on Fiio K7 Pro USB DAC. Alsamixer says "This Sound Device does not have any controls" I use Wine with sound-alsa Output directly because of SampleRate for Audio Apps, but Volume is to high and i cant change it. I can change the Pipewire or Pulse Volumes but this has no effect to the Alsa Volume. Heres the alsa-info [alsa-info.txt](https://github.com/user-attachments/files/19347989/alsa-info… Issue URL : https://github.com/alsa-project/alsa-lib/issues/444 Repository URL: https://github.com/alsa-project/alsa-lib

1 0