Am Montag, 14. Dezember 2009 20:36:13 schrieb Matthew Garrett:
> On Fri, Dec 11, 2009 at 07:47:35PM +0100, Oliver Neukum wrote:
> > Am Freitag, 11. Dezember 2009 18:14:32 schrieb Matthew Garrett:
> > > It seems slightly longer, but that could be due to the delay in the
> > > device being resumed. It's certainly on the same order (perhaps a second
> > > more)
> >
> > OK, I suspect that I forgot to mark the device busy somewhere.
> > To test this hypothesis, could you increase the interval (eg. writing
> > 10 into $DEVICE/power/autosuspend)?
>
> Yes, this results in the gap between pauses increasing to match.
Does this fix it?
Regards
Oliver
---
>From 0b72b0a05c1d950e4f35520926cc36bc01fb998a Mon Sep 17 00:00:00 2001
From: Oliver Neukum <oliver@xxxxxxxxxx>
Date: Mon, 14 Dec 2009 22:09:49 +0100
Subject: [PATCH] btusb:Prevent illtimed autosuspend
The device must be marked busy as it recieves data.
Signed-off-by: Oliver Neukum <oliver@xxxxxxxxxx>
---
drivers/bluetooth/btusb.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 4d29059..a699f09 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -307,6 +307,7 @@ static void btusb_bulk_complete(struct urb *urb)
return;
usb_anchor_urb(urb, &data->bulk_anchor);
+ usb_mark_last_busy(data->udev);
err = usb_submit_urb(urb, GFP_ATOMIC);
if (err < 0) {
--
1.6.4.2
--
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
