The device indicates the result of a read/write operation by making the
status available on a subsequent request from the driver.  This is not
ready immediately, though, so the driver is currently slamming the
device with hundreds of pointless requests before getting the expected
response.  Add a two millisecond delay before each attempt.  This is
approximately the behavior observed with version 4.2.7.1 of the Windows
driver.
Signed-off-by: Chris Rorvick <chris@rorvick.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
        line6_start_listen(line6);
 }
 
+#define LINE6_READ_WRITE_STATUS_DELAY 2  /* milliseconds */
+
 /*
        Read data from device.
 */
 
        /* Wait for data length. We'll get 0xff until length arrives. */
        do {
+               mdelay(LINE6_READ_WRITE_STATUS_DELAY);
+
                ret = usb_control_msg(usbdev, usb_rcvctrlpipe(usbdev, 0), 0x67,
                                      USB_TYPE_VENDOR | USB_RECIP_DEVICE |
                                      USB_DIR_IN,
        }
 
        do {
+               mdelay(LINE6_READ_WRITE_STATUS_DELAY);
+
                ret = usb_control_msg(usbdev, usb_rcvctrlpipe(usbdev, 0),
                                      0x67,
                                      USB_TYPE_VENDOR | USB_RECIP_DEVICE |