Hi Johan,
I got a report from a user that their device fails with
> cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22
> cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22
> cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22
> cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22
in dmesg after switching on runtime PM since their last stable update.
Reverting 140cb81ac8c625942a1d695875932c615767a526 (its stable equivalent)
resolves the issue.
commit 140cb81ac8c625942a1d695875932c615767a526
Author: Johan Hovold <jhovold@xxxxxxxxx>
Date: Mon May 26 19:23:38 2014 +0200
USB: cdc-acm: fix broken runtime suspend
As far as I can tell, your patch is correct, but nevertheless, they
see this error. What is to be done?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
