mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-15 08:14:15 +08:00
d3eabe939a
As long as I investigated, some devices with BeBoB protocol version 1 can be freezed during several hundreds milliseconds after breaking connections. When accessing during the freezed time, any transaction is corrupted. In the worst case, the device is going to reboot. I can see this issue in: * Roland FA-66 * M-Audio FireWire Solo This commit expands sleep just after breaking connections to avoid the freezed time as much as possible. I note that the freeze/reboot behaviour is similar to below models: * Focusrite Saffire Pro 10 I/O * Focusrite Saffire Pro 26 I/O The above models certainly reboot after breaking connections. Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp> Link: https://lore.kernel.org/r/20191101131323.17300-2-o-takashi@sakamocchi.jp Signed-off-by: Takashi Iwai <tiwai@suse.de> |
||
---|---|---|
.. | ||
bebob_command.c | ||
bebob_focusrite.c | ||
bebob_hwdep.c | ||
bebob_maudio.c | ||
bebob_midi.c | ||
bebob_pcm.c | ||
bebob_proc.c | ||
bebob_stream.c | ||
bebob_terratec.c | ||
bebob_yamaha_terratec.c | ||
bebob.c | ||
bebob.h | ||
Makefile |