diff options
| author | Takashi Iwai <tiwai@suse.de> | 2026-09-29 14:29:25 +0200 |
|---|---|---|
| committer | Takashi Iwai <tiwai@suse.de> | 2026-09-29 17:04:51 +0200 |
| commit | b5c4823cf3e49b3419a3bc8c6715101e1ac6cc59 (patch) | |
| tree | ea4044f0d8a0354ac7359fe6f074cbbe3c319040 /tools/lib/python/kdoc/python_version.py | |
| parent | 0eee030c2c09c7a44be778de5f451d9e7a2f09c1 (diff) | |
| download | linux-next-b5c4823cf3e49b3419a3bc8c6715101e1ac6cc59.tar.gz linux-next-b5c4823cf3e49b3419a3bc8c6715101e1ac6cc59.zip | |
ALSA: usb-audio: Apply boot quirk for Behringer models generically
Jan reported that a few Behringer devices became broken since the
recent optimization to avoid usb_string() call at probe time at the
commit b364a0d23cae ("ALSA: usb-audio: Use strings in struct usb_dev
for manufacturer & co"). Interestingly, the devices seem requiring
the explicit descriptor read at probing time, and the optimization
above dropped it.
There is already a boot quirk for another model, Behringer CM1A
(1397:1234), that adds a device descriptor read, and this seems
working for them, too. As the quirk is safe and cheap, just apply the
same boot quirk to all Behringer devices for avoiding the pitfall
again.
Fixes: b364a0d23cae ("ALSA: usb-audio: Use strings in struct usb_dev for manufacturer & co")
Reported-by: Jan Lentfer <jan.lentfer@web.de>
Closes: https://lore.kernel.org/e7087d42-5e74-4d85-b1c5-b11eff235d41@web.de
Link: https://patch.msgid.link/20260929122938.1471867-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
