Bug 206063 - ALSA: usb-audio: sample rate quirk for Bose Companion 5
Summary: ALSA: usb-audio: sample rate quirk for Bose Companion 5
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jaroslav Kysela
Depends on:
Reported: 2020-01-03 15:49 UTC by Matthias Schabhüttl
Modified: 2020-05-24 13:13 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.4.7-arch1-1
Regression: No
Bisected commit-id:

Fix patch (1.18 KB, patch)
2020-01-04 11:08 UTC, Takashi Iwai
Details | Diff

Description Matthias Schabhüttl 2020-01-03 15:49:55 UTC
As per https://www.raspberrypi.org/forums/viewtopic.php?t=15872, I believe the USB ID 0x05A7 0x1020 needs to be added to quirks.c in order for me to use my Bose Companion 5 speakers. Thanks!

usb 3-1.8: 1:1: cannot get freq at ep 0x1
...the same message will flood over dmesg.

Patched it by adding snd-usb-audio.quirk_alias to as a kernel parameter to behave like 0x047F 0x02F7 (described in Raspberry Pi forums).

With this patch, ALSA stops trying to read sample rate from device,
hence no more error messages.

dmesg output after applying the patch:
usb 3-1.8: device (05a7:1020): applying quirk alias 047f:02f7
Comment 1 Takashi Iwai 2020-01-04 11:08:23 UTC
Thanks, the patch below should fix the problem without quirk option.
I'll submit and merge to upstream later.
Comment 2 Takashi Iwai 2020-01-04 11:08:58 UTC
Created attachment 286615 [details]
Fix patch
Comment 3 Matthias Schabhüttl 2020-01-06 20:29:32 UTC
Thanks for replying and applying a patch so fast!

FYI: After upgrading to newest kernel (5.4.8-arch1-1), my quirk alias is broken (again). There are no dmesg errors (e.g. "caonnot get freq at ep 0x1") though.
Comment 4 Matthias Schabhüttl 2020-01-09 01:49:49 UTC
After further investigations dmesg is throwing: "perf: interrupt took too long (2514 > 2500), lowering kernel.perf_event_max_sample_rate to 79500" messages when the sound is dropping out.
Unplugging an re-plugging the powercable of the Bose Companion 5 speakers fixes the problem (temporarily).

Note You need to log in before you can comment on or make changes to this bug.