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

Alsamixer not detecting headphones
by GitHub issues - edited 26 Feb '23

26 Feb '23

alsa-project/alsa-ucm-conf issue #283 was edited from lgmventura: I'm using the motherboard ASUS ROG Strix B760-f Gaming Wifi, which has 7.1 audio channels on the back side and connectors for an audio panel at the front of the case - a microphone and a headphones jack. When I plug my headphones into the front channels connector (at the back of the PC case) there is normal sound. When I plug it into the headphones jack (at the front of the case), it gets automatically detected by `pavucontrol`, which switches to the headphones as output, as it should be: ![image](https://user-images.githubusercontent.com/16710238/221439991-903fd90b-43b2-41a0-af7f-1ed02085238e.png) However, there is no sound. When I open `alsamixer` and choose the respective soundcard, which is weirdly called "USB audio" there, I see no volume control for the headphones, as there should be. All it shows is this: ![image](https://user-images.githubusercontent.com/16710238/221440193-381eadfb-fed9-48ad-807b-05c736b65b24.png) The only way I got to get audio output from the headphones jack is by running `aplay` and choosing the hardware directly from there `aplay -D plughw:1,1 /usr/share/sounds/alsa/Front_Center.wav` or on Audacity by selecting "USB Audio 1: (hw:1,1)" as playback device. I also tried to use JACK Audio Connection Kit, but found no configuration there that routes the audio to the headphones jack, even trying all 4 possible analogue outputs. System: - Motherboard ASUS ROG Strix B760-f Gaming Wifi - Intel core i7-13700K - Ubuntu 22.04 (freshly installed) Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/283 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Alsamixer not detecting headphones
by GitHub issues - opened 26 Feb '23

26 Feb '23

alsa-project/alsa-lib issue #304 was opened from lgmventura: I'm using the motherboard ASUS ROG Strix B760-f Gaming Wifi, which has 7.1 audio channels on the back side and connectors for an audio panel at the front of the case - a microphone and a headphones jack. When I plug my headphones into the front channels connector (at the back of the PC case) there is normal sound. When I plug it into the headphones jack (at the front of the case), it gets automatically detected by `pavucontrol`, which switches to the headphones as output, as it should be: ![image](https://user-images.githubusercontent.com/16710238/221439991-903fd90b-43b2-41a0-af7f-1ed02085238e.png) However, there is no sound. When I open `alsamixer` and choose the respective soundcard, which is weirdly called "USB audio" there, I see no volume control for the headphones, as there should be. All it shows is this: ![image](https://user-images.githubusercontent.com/16710238/221440193-381eadfb-fed9-48ad-807b-05c736b65b24.png) The only way I got to get audio output from the headphones jack is by running `aplay` and choosing the hardware directly from there `aplay -D plughw:1,1 /usr/share/sounds/alsa/Front_Center.wav` or on Audacity by selecting "USB Audio 1: (hw:1,1)" as playback device. I also tried to use JACK Audio Connection Kit, but found no configuration there that routes the audio to the headphones jack, even trying all 4 possible analogue outputs. System: - Motherboard ASUS ROG Strix B760-f Gaming Wifi - Intel core i7-13700K - Ubuntu 22.04 (freshly installed) Issue URL : https://github.com/alsa-project/alsa-lib/issues/304 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

infinite loop in src/pcm/pcm_params.c function snd_pcm_sw_params_default()
by bumpelo＠gmail.com 25 Feb '23

25 Feb '23

I found this infinite loop while playing with the test/latency.c function. When I specify too small of a minimum latency (in my case -m 256 or smaller) it winds up: at line line 2337: params->boundary = pcm->buffer_size; while (params->boundary * 2 <= LONG_MAX - pcm->buffer_size) params->boundary *= 2; return 0; but when pcm->buffer_size is zero this is an infinite loop. It does this *after* setting the scheduling to round-robin which makes the infinite loop so much more painful. The return value from this function is ignored where it's called so I'm not sure what the best fix is. I'm guessing it's a rare case since it's not been previously reported but it deserves fixing anyway.

2 1

xone mixer
by GitHub issues - opened 25 Feb '23

25 Feb '23

alsa-project/alsa-lib issue #303 was opened from molli1312: Having a few problems with the Xone32c though not sure if this is an ALSA issue or general USB stack problem. It's a USB soundcard that is supposed to have 4 inputs and 4 outputs. It seems to have 2 USB configurations (bNumConfigurations : 0x2). When plugged in, bConfigurationValue is 0x1 and only 2 inputs and 2 outputs show up. Change this value to 0x2 and it shows up (as it should) as 4 inputs and 4 outputs. I can change the bConfigurationValue with this udev rule, or with a `echo 2 /sys/bus/usb/devices/1-1.4/bConfigurationValue`: This has all been working OK on Ubuntu 20.04 running kernel 5.4.0-33-generic. However, I just updated to 5.4.0-37-generic and now there is only a single USB configuration (bNumConfigurations : 0x1) and bConfigurationValue can't be changed to 0x2: Issue URL : https://github.com/alsa-project/alsa-lib/issues/303 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

OpenBSD (and maybe other *BSDs) support (2)
by GitHub pull_request - opened 25 Feb '23

25 Feb '23

alsa-project/alsa-utils pull request #193 was opened from jg1uaa: #186 addendum. forget to fix alsactl/lock.c, this is the fix. Request URL : https://github.com/alsa-project/alsa-utils/pull/193 Patch URL : https://github.com/alsa-project/alsa-utils/pull/193.patch Repository URL: https://github.com/alsa-project/alsa-utils

1 0

hda-verb improvements for Asus Zenbook Pro Duo UX582LR
by Marcel Brouillet 25 Feb '23

25 Feb '23

Hello, I have a Asus Zenbook Pro Duo UX582LR that does not have sound out-of-the box. But with either this : hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774 hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45 hda-verb /dev/snd/hwC0D0 0x20 0x400 0x5289 Or this : hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 Then 1. I do get output from the laptop speakers ✅ 2. I do get output through a headset when pluged in (and no sound through speakers) ✅ 3. I do get input from laptop mics, *but far too high gain. *Setting the mic level to 35% in Pulse Audio is roughly good 4. Input *remains from laptop mics even when I plug in headsets* (TRRS jack) I've been OK with this for 18 months, but decided to chip in the time to solve 3 and 4 and make it available to the community. I looked at https://github.com/alsa-project/alsa-tools/tree/master/hda-verb and understand the hda-verb syntax. But *where do I find the verb arguments (strings or the above cryptic 0x477 or 0x400) ?* Do I need to read this 220 pages document ? https://www.intel.com/content/www/us/en/standards/high-definition-audio-spe… *If anyone is willing to direct me to the few verbs to try, and please tell me if there is any risk of killing my sound interface with wrong parameters, a big thank you to you.* Regards, Marcel. Hardware : Asus Zenbook Pro Duo UX582LR Software : Ubuntu Studio 22.04.2 LTS jammy. Fresh installation 10 days ago, fully updated upgraded. alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-tools/jammy,now 1.2.5-2 amd64 [installed,automatic] alsa-tools-gui/jammy,now 1.2.5-2 amd64 [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.4 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic]

1 0

[PATCH 1/3] ASoC: apple: mca: Fix final status read on SERDES reset
by Martin Povišer 24 Feb '23

24 Feb '23

From within the early trigger we are doing a reset of the SERDES unit, but the final status read is on a bad address. Add the missing SERDES unit offset in calculation of the address. Fixes: 3df5d0d97289 ("ASoC: apple: mca: Start new platform driver") Signed-off-by: Martin Povišer <povik+lin(a)cutebit.org> --- sound/soc/apple/mca.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/apple/mca.c b/sound/soc/apple/mca.c index 24381c42eb54..9cceeb259952 100644 --- a/sound/soc/apple/mca.c +++ b/sound/soc/apple/mca.c @@ -210,7 +210,7 @@ static void mca_fe_early_trigger(struct snd_pcm_substream *substream, int cmd, SERDES_CONF_SOME_RST); readl_relaxed(cl->base + serdes_conf); mca_modify(cl, serdes_conf, SERDES_STATUS_RST, 0); - WARN_ON(readl_relaxed(cl->base + REG_SERDES_STATUS) & + WARN_ON(readl_relaxed(cl->base + serdes_unit + REG_SERDES_STATUS) & SERDES_STATUS_RST); break; default: -- 2.33.0

2 3

[PATCH] ASoC: adau7118: don't disable regulators on device unbind
by Nuno Sá 24 Feb '23

24 Feb '23

The regulators are supposed to be controlled through the set_bias_level() component callback. Moreover, the regulators are not enabled during probe and so, this would lead to a regulator unbalanced use count. Fixes: ca514c0f12b02 ("ASOC: Add ADAU7118 8 Channel PDM-to-I2S/TDM Converter driver") Signed-off-by: Nuno Sá <nuno.sa(a)analog.com> --- Note this was only checked by code inspection but unless I'm missing something, it looks clear this could happen by just insmod + rmmod the module. sound/soc/codecs/adau7118.c | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/sound/soc/codecs/adau7118.c b/sound/soc/codecs/adau7118.c index bbb097249887..a663d37e5776 100644 --- a/sound/soc/codecs/adau7118.c +++ b/sound/soc/codecs/adau7118.c @@ -444,22 +444,6 @@ static const struct snd_soc_component_driver adau7118_component_driver = { .endianness = 1, }; -static void adau7118_regulator_disable(void *data) -{ - struct adau7118_data *st = data; - int ret; - /* - * If we fail to disable DVDD, don't bother in trying IOVDD. We - * actually don't want to be left in the situation where DVDD - * is enabled and IOVDD is disabled. - */ - ret = regulator_disable(st->dvdd); - if (ret) - return; - - regulator_disable(st->iovdd); -} - static int adau7118_regulator_setup(struct adau7118_data *st) { st->iovdd = devm_regulator_get(st->dev, "iovdd"); @@ -481,8 +465,7 @@ static int adau7118_regulator_setup(struct adau7118_data *st) regcache_cache_only(st->map, true); } - return devm_add_action_or_reset(st->dev, adau7118_regulator_disable, - st); + return 0; } static int adau7118_parset_dt(const struct adau7118_data *st) -- 2.39.2

2 1

[syzbot] [alsa?] kernel BUG in __vunmap
by syzbot 23 Feb '23

23 Feb '23

Hello, syzbot found the following issue on: HEAD commit: a5541c0811a0 Merge branch 'for-next/core' into for-kernelci git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=12b4018b880000 kernel config: https://syzkaller.appspot.com/x/.config?x=cbd4e584773e9397 dashboard link: https://syzkaller.appspot.com/bug?extid=656c0cde55a9d107a76f compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: arm64 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/4b7702208fb9/disk-a5541c08.raw… vmlinux: https://storage.googleapis.com/syzbot-assets/9ec0153ec051/vmlinux-a5541c08.… kernel image: https://storage.googleapis.com/syzbot-assets/6f8725ad290a/Image-a5541c08.gz… IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+656c0cde55a9d107a76f(a)syzkaller.appspotmail.com ------------[ cut here ]------------ kernel BUG at mm/vmalloc.c:2707! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 1 PID: 9210 Comm: syz-executor.0 Not tainted 6.1.0-rc8-syzkaller-33330-ga5541c0811a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __vunmap+0x488/0x4cc mm/vmalloc.c:2707 lr : __vunmap+0x488/0x4cc mm/vmalloc.c:2707 sp : ffff800013d73ba0 x29: ffff800013d73bb0 x28: 00000000000c0002 x27: 0000000000002000 x26: ffff0000c5a44d68 x25: ffff0000c6a14080 x24: ffff00012b5ed000 x23: 0000000000000001 x22: 0000000000000200 x21: 0000000000000000 x20: ffff80000cbdd3b4 x19: ffff0001268cfa00 x18: 0000000000000000 x17: 0000000000000000 x16: ffff80000dbe6158 x15: ffff000114e01a40 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: ff808000084b647c x10: 0000000000000000 x9 : ffff8000084b647c x8 : ffff000114e01a40 x7 : ffff8000084bf4d4 x6 : 0000000000000000 x5 : 0000000000000080 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 0000000000000000 x1 : ffff80000cbaae40 x0 : 0000000000000000 Call trace: __vunmap+0x488/0x4cc mm/vmalloc.c:2707 __vfree mm/vmalloc.c:2761 [inline] vfree+0xb0/0xfc mm/vmalloc.c:2792 snd_dma_vmalloc_free+0x20/0x30 sound/core/memalloc.c:356 snd_dma_free_pages+0x84/0xc0 sound/core/memalloc.c:127 do_free_pages sound/core/pcm_memory.c:65 [inline] snd_pcm_lib_free_pages+0xa0/0x12c sound/core/pcm_memory.c:471 do_hw_free sound/core/pcm_native.c:876 [inline] snd_pcm_release_substream+0x15c/0x1dc sound/core/pcm_native.c:2705 snd_pcm_oss_release_file sound/core/oss/pcm_oss.c:2413 [inline] snd_pcm_oss_release+0x98/0x130 sound/core/oss/pcm_oss.c:2592 __fput+0x198/0x3e4 fs/file_table.c:320 ____fput+0x20/0x30 fs/file_table.c:348 task_work_run+0x100/0x148 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] do_notify_resume+0x174/0x1f0 arch/arm64/kernel/signal.c:1132 prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline] el0_svc+0x9c/0x150 arch/arm64/kernel/entry-common.c:638 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584 Code: 17ffff1f 97f7c16d 17ffff18 97f7c16b (d4210000) ---[ end trace 0000000000000000 ]--- --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller(a)googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

1 0

Re: Firewire Audio Interface
by Takashi Sakamoto 23 Feb '23

23 Feb '23

Hi, (C.C.ed to alsa-devel) On Wed, Feb 22, 2023 at 11:51:23AM -0500, mj@mj wrote: > Hey man thanks so much for the reply! > > Why TC put the phantom switch in the software instead of on the > hardware unit I can’t figure out! > > I think I’m just going to use it a 2-in 2-out interface without > the phantom. > > A friend of mine looked at the circuit board and told me it > would be too difficult to put a switch for the phantom power in it. > > Thanks again for the reply! If it is Desktop Konnekt 6, node offset 0x'ffff'e0a0'103c has the 32 bit value to express the state of phantom powering. If it is 0, disabled, else enabled. Quadlet write asynchronous transaction can change the state, but I have never used MacOs to operate any node in IEEE 1394 bus. I know some developer and user for the craft driver; e.g. * Re: [alsa-devel] Tascam Coding Inquiry * https://lore.kernel.org/alsa-devel/20200108095430.GA16741@workstation/ I think it your help to contact to them. Especially Paul Neyrinck[1] seems to complete his work for the craft driver of Digidesign Digi 002/003 family in MacOS. They are different hardware from yours, while he will help you to execute the simple read/write transaction to a certain offset of it. [1] https://neyrinck.com/ Regards Takashi Sakamoto

1 0