Comment # 11 on bug 1206766 from Takashi Iwai

Thanks.  I guess the problem is seen in the log:

[  297.105975] usb 1-2: 2:0: usb_set_interface failed (-110)
[  302.253426] usb 1-2: 1:1: cannot get freq (v2/v3): err -110
[  307.377355] usb 1-2: 1:1: cannot set freq 48000 (v2/v3): err -110
[  312.493318] usb 1-2: 1:1: cannot get freq (v2/v3): err -110
[  317.613261] usb 1-2: 1:1: cannot set freq 48000 (v2/v3): err -110
[  322.733459] usb 1-2: 1:1: cannot get freq (v2/v3): err -110
[  327.857144] usb 1-2: 1:1: cannot set freq 48000 (v2/v3): err -110
[  332.973058] usb 1-2: 1:1: cannot get freq (v2/v3): err -110
[  338.093295] usb 1-2: 1:1: cannot set freq 48000 (v2/v3): err -110
[  343.213253] usb 1-2: 1:1: cannot get freq (v2/v3): err -110
[  348.333142] usb 1-2: 1:1: cannot set freq 48000 (v2/v3): err -110

... which indicates that the USB device becomes unstable and refuses to set up
something with -ETIMEDOUT error.

I'm not sure whether this is caused by the USB audio driver update or by some
change in USB core (or other) side for now.

I'll try to create a KMP that replaces the USB audio driver with 6.0.x
equivalence, and we can check it at first.  Let's see.