Hi Oliver, > > > What is the current status of btusb auto suspend? btusb not having this > > > feature basically renders BT useless on mobile devices. > > > > > > I found some rfc patches and discussion over on linux-pm/-usb but > > > couldn't find a clear consensus. > > > > I think none of the patches apply anymore. So they have to be redone > > against the latest -rc4 kernel or bluetooth-testing.git. > > I am porting forward to Linus' tree. I thought they'd safely wait for > the next merge window. I can push them into bluetooth-testing.git tree. > > We had some battles with broken Bluetooth hardware that requires to keep > > the interrupt and bulk URBs in fly, because otherwise the firmware > > inside the controller can't sync them up and times out. These are all > > fixed now, but nobody has looked at the auto suspend stuff. Feel free to > > It will have to be changed to work with those buggy devices. > Do you have a pointer to a page describing the problem in detail? The problem is that the interrupt URBs and bulk URBs for RX have to be always scheduled. Not matter if we have an ACL link or. Once the device is up they have to there. Some devices just don't like it if we only have interrupt URBs. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
