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

[alsa-devel] alsaloop problems; ALSA streaming tutorial (resend)
by frederik＠ofb.net 29 Oct '18

29 Oct '18

Dear Mark (cc'ing ALSA-user, ALSA-devel) Thank you for your tutorial http://www.pogo.org.uk/~mark/trx/streaming-desktop-audio.html I found it helpful and clearly-written (although missing a "}" brace and I think it should be "-P" instead of "-p"...). I got as far as trying the 'alsaloop' example. It seems very finicky, sometimes I am able to play a test.wav cleanly through the loopback device, and sometimes there are a lot of crackles and I get errors like playback hw:0: change avail_min=2968 playback hw:0: change avail_min=2972 playback hw:0: change avail_min=2976 underrun for playback hw:0 last write before 9.8370ms, queued 10.0000ms/0.0000ms -> missing -0.1630ms expected 10.0000ms, processing 0.1910ms, max missing 0.0443ms last wake 0.0350ms, last check 0.0350ms, avail_min 32.0000ms max buf 40.0000ms, pfilled 0.0000ms, cfilled 10.0000ms job started before 0.0110ms For 'aplay' invocations where there are errors, it generally never recovers; the whole (10 second) wav file is played with crackles and errors being printed. I tried to figure out if this is due to some different rate settings being chosen at random with each 'aplay' invocation, but all the alsaloop debugging output looks the same between working and non-working runs of aplay (except for the above underrun errors). I also tried various settings for -A and -S in 'alsaloop', but nothing would alleviate this problem. The only thing that fixes it is to change the latency '-t' setting to a higher value than the default 10ms. However this seems like a bad solution, given that it is able (50% of the time) to play a whole sound file at the lower latency with no errors; I would rather have it recover from the underruns when they happen, than increase the latency for every invocation. Enabling realtime via the Arch Wiki info (a bit tricky as I had to edit some of the files by hand) didn't change this behavior. I also encountered a problem when trying to make alsaloop output to a dmix device. I wanted to have it output to dmix so that I could use my audio normally while experimenting with alsaloop. I got a "Poll FD initialization failed." error: playback plug:hw0mix/capture hubcap sync type: CAPTRATESHIFT New pitch for playback plug:hw0mix/capture hubcap: 1.00000000 (min/max samples = 0/0) underrun for playback plug:hw0mix last write before 19.7440ms, queued -1.0000ms/-1.0000ms -> missing -1.0000ms expected 10.0000ms, processing 0.0290ms, max missing 0.0000ms last wake 1539883911239.1819ms, last check 19.6460ms, avail_min 2.5000ms max buf 250.0000ms, pfilled 0.0000ms, cfilled 0.0000ms job started before 0.0310ms Poll FD initialization failed. Is this error understood? I would have thought that enough others would also have been wanting to use alsaloop in such a simple configuration, to warrant a better error message. I'm somewhat confused by the alsaloop manual page, my version says it is from "5 Aug 2010" but it has glaring errors, it says "-B" is a synonym for "--buffer" but alsaloop tells me "alsaloop: invalid option -- 'B'". Also it says that I can use "-c" to set both channels and rate. Are these typos really unfixed for eight years? Here are the commands I used: $ alsaloop -C hubcap -P hw:0 -v -v -U |& tee alsaloloop.out ... $ aplay -v test.wav |& tee aplay.out ... $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version k4.14.71-1-lts. The earlier version of this email had output files attached, but they caused the message to be held for "moderator approval". Here are some HTTP versions of the same files: alsaloop.out: http://ix.io/1pUj aplay.out: http://ix.io/1pUk asound-remote (the config): http://ix.io/1pUl I think I'll investigate network audio with JACK next but I wanted to share my experiences in case there is something I'm doing wrong here, or in case there are bugs that can be fixed in ALSA. Thank you, Frederick

2 2

Re: [alsa-devel] [linux-sunxi] [BUG] On Allwinner A20 Board Cubietruck distorted SPDIF opical output
by Markus Mitsch 27 Oct '18

27 Oct '18

hi. i posted my answer wrong so here is my finding: i made the output work by disabling the sigma delta modulation. after compiling the kernel i can output through spdif with any rate. greetings markus 2018-05-26 18:38 GMT+02:00 Markus Mitsch <markusmitsch86(a)googlemail.com>: > 2018-05-26 16:57 GMT+02:00 Markus Mitsch <markusmitsch86(a)googlemail.com>: >> 2018-05-23 17:12 GMT+02:00 Code Kipper <codekipper(a)gmail.com>: >>> Hi All, >>> I can see that the problem was introduced somewhere here >>> >>> DOESN'T WORK >>> ffc3eb6f3a83 Merge tag 'sunxi-clk-for-4.15' of >>> https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into >>> clk-next >>> ae74ac082886 Merge tag 'clk-v4.15-exynos-pm' of >>> git://git.kernel.org/pub/scm/linux/kernel/git/snawrocki/clk into >>> clk-next >>> faa865f18cb7 Merge tag 'clk-v4.15-samsung' of >>> git://git.kernel.org/pub/scm/linux/kernel/git/snawrocki/clk into >>> clk-next >>> f09a6b86fdae Merge tag 'clk-renesas-for-v4.15-tag1' of >>> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers >>> into clk-next >>> 4328a2186e51 clk: sunxi-ng: sun4i: Export video PLLs >>> 553c7d5ba2fe clk: sunxi-ng: Add A83T display clocks >>> 7679eb20353d clk: samsung: Add a separate driver for Exynos4412 ISP clocks >>> 8ca8ac102484 clk: samsung: Add dt bindings for Exynos4412 ISP clock controller >>> 75920aac275a clk: samsung: Instantiate Exynos4412 ISP clocks only when available >>> 24ea78a09f89 clk: sunxi-ng: sun8i: a23: Use sigma-delta modulation for audio PLL >>> ee6501d69217 clk: sunxi-ng: sun6i: Use sigma-delta modulation for audio PLL >>> 042f7f8f9715 clk: sunxi-ng: sun5i: Use sigma-delta modulation for audio PLL >>> de3448519194 clk: sunxi-ng: sun4i: Use sigma-delta modulation for audio PLL >>> a5e3e2b2ef85 clk: sunxi-ng: sun8i: h3: Use sigma-delta modulation for audio PLL >>> 392ba5fafcdf clk: sunxi-ng: nm: Add support for sigma-delta modulation >>> 05d2eaac96d4 clk: sunxi-ng: Add sigma-delta modulation support >>> 4cdbc40d64d4 clk: sunxi-ng: nm: Check if requested rate is supported >>> by fractional clock >>> d51fe3ba9773 clk: sunxi-ng: sun5i: Fix bit offset of audio PLL post-divider >>> 4e8975cbb516 clk: samsung: exynos5433: mark PM functions as __maybe_unused >>> a4f21e9ceb5c clk: samsung: Remove obsolete clkdev alias support >>> 45d882daf88a clk: samsung: Add explicit MPLL, EPLL clkdev aliases in >>> S3C2443 driver >>> cd05417f728b clk: samsung: Rework clkdev alias handling in S3C2443 driver >>> efea8d377184 clk: samsung: Rework clkdev alias handling in Exynos5440 driver >>> 36ba48240b19 clk: samsung: Drop useless alias in Exynos5420 clk driver >>> 29964890f31c clk: samsung: Remove clkdev alias support in Exynos5250 clk driver >>> 6de08891c896 clk: samsung: Remove double assignment of CLK_ARM_CLK in >>> Exynos4 driver >>> 58f4a5ff3a62 clk: samsung: Remove clkdev alias support in Exynos4 clk driver >>> c9194fb623b0 clk: samsung: Remove support for obsolete Exynos4212 CPU clock >>> d5cd103b06f9 clk: samsung: Remove support for Exynos4212 SoCs in >>> Exynos CLKOUT driver >>> 7c4f63ec94a1 clk: sunxi-ng: a83t: Fix invalid csi-mclk mux offset >>> WORKS >>> 0a4e632b6f9d Merge branch 'clk-fixes' into clk-next >>> >>> BR, >>> CK >>> >>> >>> On 22 May 2018 at 21:27, Code Kipper <codekipper(a)gmail.com> wrote: >>>> Hi Markus, >>>> I've been able to reproduce this on my A31 board with linux-next(plays >>>> at 44100 but not at 96K)so it is an issue. I also tested the same code >>>> on my A64 and it worked fine, The blocks are very similar so it maybe >>>> a clocking issue, I'll look into this. >>>> BR, >>>> CK >>>> >>>> On 21 May 2018 at 20:17, Markus Mitsch <markusmitsch86(a)googlemail.com> wrote: >>>>> 2018-05-21 15:17 GMT+02:00 Maxime Ripard <maxime.ripard(a)bootlin.com>: >>>>>> On Mon, May 21, 2018 at 02:43:55PM +0200, Markus Mitsch wrote: >>>>>>> 2018-05-21 11:43 GMT+02:00 Markus Mitsch <markusmitsch86(a)googlemail.com>: >>>>>>> >>> Hello, >>>>>>> >>> >>>>>>> >>> i have a new problem. if i want to output sound from optical i get >>>>>>> >>> distorted sound. At 44.1 khz its like an old vinly, but at 48 khz and >>>>>>> >>> higher it is very bad. thanks in advance for your time. >>>>>>> > >>>>>>> >> Hi Markus, >>>>>>> >> I haven't tested it for a while but when I did it worked as high as >>>>>>> >> 96K with no issues. Does it work ok with the original cubietruck >>>>>>> >> software?, >>>>>>> >> CK >>>>>>> > >>>>>>> > Hello, >>>>>>> > i am using arch linux with mainline kernel 4.16.8. parhaps i can try >>>>>>> > today with official image. >>>>>>> > mfg >>>>>>> >>>>>>> Hi. >>>>>>> So, with debian image from 2014 with 3.4.79 kernel the sound is clear >>>>>>> up to 96 khz. >>>>>> >>>>>> You said that it is a new problem, when was it introduced? Could you >>>>>> bisect the issue? >>>>>> >>>>>> Maxime >>>>> >>>>> Hello. >>>>> I dont know since when this problem appears. When saying "new" i >>>>> refered to my older post. I tried to look into the dts file and the >>>>> code >>>>> but i am afraid this is a bit too high for me. I can say that the >>>>> analog output works, even at high sampling rates. >>>>> And I have read something about a clock source could be the problem. >>>>> I'm sorry I can't tell you any more. >>>>> >>>>> mfg >>>>> Markus >> >> Hello, >> i tried undoing part of the commit >> de3448519194 clk: sunxi-ng: sun4i: Use sigma-delta modulation for audio PLL >> by setting the value for the divider from 1 to 4 again on both places. >> with no success. >> >> markus > > i now had a little success. the output works!! > i disabled the sigma-delta support by making > ccu_sdm_helper_enable in drivers/clk/sunxi-ng/ccu_sdm.c return imediately. > > markus

2 2

[alsa-devel] [PATCH] ALSA: dice: fix to wait for releases of all ALSA character devices
by Takashi Sakamoto 27 Oct '18

27 Oct '18

In a development period for Linux kernel v4.20, drivers in ALSA firewire stack were changed to wait for releases of all ALSA character devices at .remove callback of bus driver. However, ALSA dice driver is partly out of this change. This bug can bring fault to user process which holds the last of character device in unplugging. This commit fixes the driver to wait in the callback. Fixes: 61ccc6f6b27c ('ALSA: firewire: block .remove callback of bus driver till all of ALSA character devices are released') Signed-off-by: Takashi Sakamoto <o-takashi(a)sakamocchi.jp> --- sound/firewire/dice/dice.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/firewire/dice/dice.c b/sound/firewire/dice/dice.c index 0f6dbcffe711..ed50b222d36e 100644 --- a/sound/firewire/dice/dice.c +++ b/sound/firewire/dice/dice.c @@ -240,8 +240,8 @@ static void dice_remove(struct fw_unit *unit) cancel_delayed_work_sync(&dice->dwork); if (dice->registered) { - /* No need to wait for releasing card object in this context. */ - snd_card_free_when_closed(dice->card); + // Block till all of ALSA character devices are released. + snd_card_free(dice->card); } mutex_destroy(&dice->mutex); -- 2.19.1

2 1

[alsa-devel] QA issue with media-sound/alsa-utils-1.1.7 Gentoo package
by Francesco Turco 27 Oct '18

27 Oct '18

The Portage package manager returns the following QA warning when installing the media-sound/alsa-utils-1.1.7 Gentoo package: * QA Notice: Package triggers severe warnings which indicate that it * may exhibit random runtime failures. * ../alsamixer/volume_mapping.c:116:15: warning: incompatible implicit declaration of built-in function ‘exp10’ * ../alsamixer/volume_mapping.c:151:14: warning: incompatible implicit declaration of built-in function ‘exp10’ * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: https://alsa-project.org/ -- https://fturco.gitlab.io/

1 0

[alsa-devel] [PATCH 0/2] Introduce dmic mode switch delay parameter
by Jenny TC 25 Oct '18

25 Oct '18

Some DMICs need clock to be running for a specified duration as per the DMIC spec to complete the mode transition like sleep to mormal, off to normal etc. Jenny TC (2): ASoC: dmic: Enable ACPI device entry ASoC: dmic: Introduce mode switch delay sound/soc/codecs/dmic.c | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) -- 1.9.1

6 11

[alsa-devel] [PATCH] alsa-utils: fix identation indentation on speaker-test.c
by Eduardo Abinader 25 Oct '18

25 Oct '18

Signed-off-by: Eduardo Abinader <eduardoabinader(a)gmail.com> --- speaker-test/speaker-test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/speaker-test/speaker-test.c b/speaker-test/speaker-test.c index 773af0a..4aac30c 100644 --- a/speaker-test/speaker-test.c +++ b/speaker-test/speaker-test.c @@ -1207,7 +1207,7 @@ int main(int argc, char *argv[]) { gettimeofday(&tv1, NULL); for(chn = 0; chn < channels; chn++) { - int channel = get_speaker_channel(chn); + int channel = get_speaker_channel(chn); printf(" %d - %s\n", channel, get_channel_name(channel)); err = write_loop(handle, channel, ((rate*3)/period_size), frames); -- 2.17.1

2 1

[alsa-devel] [PATCH v2 - AAF PCM plugin 0/7] Introduce AVTP Audio Format (AAF) plugin
by Andre Guedes 25 Oct '18

25 Oct '18

Hi all, This new version addresses the feedback from v1 and fixes a bug on capture mode. Code-wise, the changes are very trivial, no major diffs. Below follows the highlights: * Standard headers like linux/if_ether.h are now checked by configure script. * The 'static' modifier was added to array variables in aaf_hw_constraint(). * aaf_close() callback was simplified. * aaf_rx_pdu() was modified so it doesn't return an error in case the number of bytes read by recv() is different from aaf->pdu_size. This is an expected situation and it means the received AVTPDU doesn't belong to the AAF stream the plugin is interested in so it should simply drop that AVTPDU. This fixes a bug when running multiple streams (with different AVPTU sizes) concurrently. Additionally, this new version improves the instructions in doc/aaf.txt in order to make it easier to test the plugin. Anyone should be able to test it just by copying and pasting the instructions. To recap what has been discussed about the plugin so far, check the comments in RFC and PATCH series archive [1-3]. All versions of this series can be also found in my alsa-plugins tree in github [4]. Regards, Andre [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2018-August/139494.html [2] http://mailman.alsa-project.org/pipermail/alsa-devel/2018-September/140290.… [3] http://mailman.alsa-project.org/pipermail/alsa-devel/2018-October/140667.ht… [4] https://github.com/aguedes/alsa-plugins Andre Guedes (7): aaf: Introduce plugin skeleton aaf: Load configuration parameters aaf: Implement Playback mode support aaf: Prepare for Capture mode support aaf: Implement Capture mode support aaf: Implement dump() ioplug callback aaf: Add support for direct read/write transfers Makefile.am | 3 + aaf/Makefile.am | 9 + aaf/pcm_aaf.c | 1200 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ configure.ac | 11 + doc/aaf.txt | 157 ++++++++ 5 files changed, 1380 insertions(+) create mode 100644 aaf/Makefile.am create mode 100644 aaf/pcm_aaf.c create mode 100644 doc/aaf.txt -- 2.14.4

3 11

[alsa-devel] KASAN: use-after-free Read in snd_seq_timer_interrupt
by syzbot 24 Oct '18

24 Oct '18

Hello, syzbot found the following crash on: HEAD commit: 44786880df19 Merge branch 'parisc-4.20-1' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=178c8bad400000 kernel config: https://syzkaller.appspot.com/x/.config?x=5071a2e3cb82c943 dashboard link: https://syzkaller.appspot.com/bug?extid=d5136d4d3240cbe45a2a compiler: gcc (GCC) 8.0.1 20180413 (experimental) Unfortunately, I don't have any reproducer for this crash yet. IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+d5136d4d3240cbe45a2a(a)syzkaller.appspotmail.com ================================================================== BUG: KASAN: use-after-free in snd_seq_timer_interrupt+0x364/0x3e0 sound/core/seq/seq_timer.c:145 Read of size 8 at addr ffff8801cf71c118 by task syz-executor0/24085 CPU: 1 PID: 24085 Comm: syz-executor0 Not tainted 4.19.0+ #300 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x244/0x39d lib/dump_stack.c:113 print_address_description.cold.7+0x9/0x1ff mm/kasan/report.c:256 kasan_report_error mm/kasan/report.c:354 [inline] kasan_report.cold.8+0x242/0x309 mm/kasan/report.c:412 __asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:433 snd_seq_timer_interrupt+0x364/0x3e0 sound/core/seq/seq_timer.c:145 snd_timer_interrupt+0x9ff/0x1660 sound/core/timer.c:855 snd_timer_s_function+0xcd/0x130 sound/core/timer.c:1094 call_timer_fn+0x272/0x920 kernel/time/timer.c:1326 expire_timers kernel/time/timer.c:1363 [inline] __run_timers+0x7e5/0xc70 kernel/time/timer.c:1682 run_timer_softirq+0x52/0xb0 kernel/time/timer.c:1695 __do_softirq+0x308/0xb7e kernel/softirq.c:292 invoke_softirq kernel/softirq.c:373 [inline] irq_exit+0x17f/0x1c0 kernel/softirq.c:413 exiting_irq arch/x86/include/asm/apic.h:536 [inline] smp_apic_timer_interrupt+0x1cb/0x760 arch/x86/kernel/apic/apic.c:1061 apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:801 </IRQ> RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:761 [inline] RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline] RIP: 0010:_raw_spin_unlock_irqrestore+0xaf/0xd0 kernel/locking/spinlock.c:184 Code: 30 f6 31 89 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 28 48 83 3d 28 cd 7c 01 00 74 15 48 89 df 57 9d <0f> 1f 44 00 00 eb ad e8 7c 52 4b f9 eb bb 0f 0b 0f 0b e8 8a 54 0e RSP: 0018:ffff880181eaf508 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff13 RAX: dffffc0000000000 RBX: 0000000000000282 RCX: 0000000000000000 RDX: 1ffffffff1263ec6 RSI: 0000000000000001 RDI: 0000000000000282 RBP: ffff880181eaf518 R08: ffff88018378a140 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff8801c0b94ac0 R13: ffff8801c0b94300 R14: ffff8801daf2cc40 R15: 0000000000000001 try_to_wake_up+0x10a/0x12e0 kernel/sched/core.c:2056 wake_up_process kernel/sched/core.c:2124 [inline] wake_up_q+0xa4/0x100 kernel/sched/core.c:440 futex_wake+0x61f/0x760 kernel/futex.c:1556 do_futex+0x2e4/0x26d0 kernel/futex.c:3533 __do_sys_futex kernel/futex.c:3589 [inline] __se_sys_futex kernel/futex.c:3557 [inline] __x64_sys_futex+0x472/0x6a0 kernel/futex.c:3557 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x457569 Code: fd b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 cb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:0000000000a3fbf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca RAX: ffffffffffffffda RBX: 000000000072bfa0 RCX: 0000000000457569 RDX: 0000000000000000 RSI: 0000000000000081 RDI: 000000000072bfa8 RBP: 00000000000003b7 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000a3fcb0 R11: 0000000000000246 R12: 000000000072bfac R13: 000000000072bfac R14: 0000000000000003 R15: 0000000000000001 Allocated by task 24073: save_stack+0x43/0xd0 mm/kasan/kasan.c:448 set_track mm/kasan/kasan.c:460 [inline] kasan_kmalloc+0xc7/0xe0 mm/kasan/kasan.c:553 kmem_cache_alloc_trace+0x152/0x750 mm/slab.c:3620 kmalloc include/linux/slab.h:513 [inline] kzalloc include/linux/slab.h:707 [inline] queue_new sound/core/seq/seq_queue.c:113 [inline] snd_seq_queue_alloc+0xab/0x5b0 sound/core/seq/seq_queue.c:185 snd_seq_ioctl_create_queue+0xb0/0x320 sound/core/seq/seq_clientmgr.c:1522 snd_seq_ioctl+0x253/0x440 sound/core/seq/seq_clientmgr.c:2138 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702 __do_sys_ioctl fs/ioctl.c:709 [inline] __se_sys_ioctl fs/ioctl.c:707 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 24072: save_stack+0x43/0xd0 mm/kasan/kasan.c:448 set_track mm/kasan/kasan.c:460 [inline] __kasan_slab_free+0x102/0x150 mm/kasan/kasan.c:521 kasan_slab_free+0xe/0x10 mm/kasan/kasan.c:528 __cache_free mm/slab.c:3498 [inline] kfree+0xcf/0x230 mm/slab.c:3813 queue_delete+0x90/0xb0 sound/core/seq/seq_queue.c:156 snd_seq_queue_client_leave+0x36/0x170 sound/core/seq/seq_queue.c:584 seq_free_client1.part.9+0xf4/0x270 sound/core/seq/seq_clientmgr.c:263 seq_free_client1 sound/core/seq/seq_clientmgr.c:256 [inline] seq_free_client+0x82/0x100 sound/core/seq/seq_clientmgr.c:285 snd_seq_release+0x51/0xe0 sound/core/seq/seq_clientmgr.c:366 __fput+0x385/0xa30 fs/file_table.c:278 ____fput+0x15/0x20 fs/file_table.c:309 task_work_run+0x1e8/0x2a0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:193 [inline] exit_to_usermode_loop+0x318/0x380 arch/x86/entry/common.c:166 prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline] syscall_return_slowpath arch/x86/entry/common.c:268 [inline] do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe The buggy address belongs to the object at ffff8801cf71c0c0 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 88 bytes inside of 512-byte region [ffff8801cf71c0c0, ffff8801cf71c2c0) The buggy address belongs to the page: page:ffffea00073dc700 count:1 mapcount:0 mapping:ffff8801da800940 index:0x0 flags: 0x2fffc0000000100(slab) raw: 02fffc0000000100 ffffea00073a4fc8 ffffea000761f4c8 ffff8801da800940 raw: 0000000000000000 ffff8801cf71c0c0 0000000100000006 0000000000000000 kobject: 'loop5' (00000000172d3417): kobject_uevent_env page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8801cf71c000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff8801cf71c080: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb > ffff8801cf71c100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8801cf71c180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8801cf71c200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== --- This bug 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 bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot.

1 0

[alsa-devel] [PATCH v4 00/14] ASoC: Add support to WCD9335 Audio Codec
by srinivas.kandagatla＠linaro.org 24 Oct '18

24 Oct '18

From: Srinivas Kandagatla <srinivas.kandagatla(a)linaro.org> Thankyou for reviewing v3 patchset, here is v4 addressing comments from v3. Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC. It is integrated in multiple Qualcomm SoCs like: MSM8996, MSM8976, and MSM8956 chipsets. WCD9335 had multiple functional blocks, like: Soundwire controller, interrupt mux, pin controller, Audio codec, MBHC, MAD(Mic activity Detection), Ultrasonic proximity and pen detection, Battery-voltage monitoring and Codec processing engine. Currently this patchset has been only tested with SLIMbus interface due to hardware avaiablity, but it can be easily made to work with both SLIMbus and I2C/I2S. This patchset adds very basic playback and capture support witout much fancy features. New features will be added once the basic support is in. This patchset is tested on top of linux-next on DB820c for both playback , capture paths and MBHC. Some parts of the code has been inherited from Qualcomm andriod kernel, so credits to various authors. WCD9335 can be interfaced via I2S/I2C or SLIMbus. Here is my test branch incase someone want to try this out: https://git.linaro.org/people/srinivas.kandagatla/linux.git/log/?h=wcd9335 Thanks, Srini Changes since v3 (https://lkml.org/lkml/2018/9/4/318/) - Updated mbhc dt bindings according to Robs Comments. - Added a cleanup patch to common up fixups. - Addressed various comments on mfd driver by Lee Jones. - Added acks on bindings and irq support. - fixed module loading Srinivas Kandagatla (14): ASoC: dt-bindings: update wcd9335 bindings. mfd: wcd9335: add support to wcd9335 core mfd: wcd9335: add wcd irq support ASoC: wcd9335: add support to wcd9335 codec ASoC: wcd9335: add CLASS-H Controller support ASoC: wcd9335: add basic controls ASoC: wcd9335: add playback dapm widgets ASoC: wcd9335: add capture dapm widgets ASoC: wcd9335: add audio routings ASoC: dt-bindings: Add WCD9335 MBHC specific properties ASoC: wcd9335: add mbhc support ASoC: apq8096: add slim support ASoC: apq8096: add headset JACK support ASoC: qcom: common: move be_hw_fixup to common .../devicetree/bindings/sound/qcom,wcd9335.txt | 30 +- drivers/mfd/Kconfig | 13 + drivers/mfd/Makefile | 4 + drivers/mfd/wcd9335-core.c | 394 ++ include/linux/mfd/wcd9335/registers.h | 640 +++ include/linux/mfd/wcd9335/wcd9335.h | 81 + sound/soc/codecs/Kconfig | 5 + sound/soc/codecs/Makefile | 2 + sound/soc/codecs/wcd-clsh-v2.c | 577 +++ sound/soc/codecs/wcd-clsh-v2.h | 49 + sound/soc/codecs/wcd9335.c | 5241 ++++++++++++++++++++ sound/soc/qcom/apq8096.c | 128 +- sound/soc/qcom/common.c | 17 + sound/soc/qcom/sdm845.c | 22 +- 14 files changed, 7168 insertions(+), 35 deletions(-) create mode 100644 drivers/mfd/wcd9335-core.c create mode 100644 include/linux/mfd/wcd9335/registers.h create mode 100644 include/linux/mfd/wcd9335/wcd9335.h create mode 100644 sound/soc/codecs/wcd-clsh-v2.c create mode 100644 sound/soc/codecs/wcd-clsh-v2.h create mode 100644 sound/soc/codecs/wcd9335.c -- 2.9.3

5 21

[alsa-devel] [asoc:for-4.20 519/528] sound/soc/stm/stm32_sai_sub.c:393:26-32: ERROR: application of sizeof to pointer
by kbuild test robot 24 Oct '18

24 Oct '18

tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-4.20 head: 6be0f96d799f487f05eb412d362d5a1747d665c2 commit: 8307b2afd386ccce369821daa2196068c47fe8cd [519/528] ASoC: stm32: sai: set sai as mclk clock provider coccinelle warnings: (new ones prefixed by >>) >> sound/soc/stm/stm32_sai_sub.c:393:26-32: ERROR: application of sizeof to pointer -- >> sound/soc/stm/stm32_sai_sub.c:343:5-8: WARNING: Unsigned expression compared with zero: div < 0 Please review and possibly fold the followup patch. --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation

3 2