On Mon, Aug 6, 2018 at 2:59 PM, Oliver Neukum <oneukum@xxxxxxxx> wrote: > On Sa, 2018-08-04 at 23:10 +0530, Muni Sekhar wrote: >> >> Unloading the driver and killing the 'fwupd' daemon resulted that >> device to go into runtime suspend. Here I noticed that both the >> operations(i.e. rmmod btusb & kill -9 <pid of fwupd>) are mandatory to >> device to go into runtime suspend. I'd like to understand how the >> driver & daemon are preventing the device to go into suspend mode, can >> you please explain me on this? > > Hi, > > btusb has support for autosuspend. > > 1. Please check whether your device supports remote wake up and isn't > quirky Right now my device does not support remote wakeup, need firmware support for this. Once I receive the firmware then i'll give a try. > 2. Try a 'hciconfig hciX down' (with X for your number > > HTH > Oliver > -- Thanks, Sekhar -- 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
