Am Mittwoch, den 16.08.2017, 11:37 +0200 schrieb Marcel Holtmann: > Hi Oliver, > > > > > BT-Controller connected as platform non-root-hub device and > > usb-driver initialize such device with wakeup disabled, > > Ref. usb_new_device(). > > > > At present wakeup-capability get enabled by hid-input device from usb > > function driver(e.g. BT HID device) at runtime. Again some functional > > driver does not set usb-wakeup capability(e.g LE HID device implement > > as HID-over-GATT), and can't wakeup the host on USB. > > > > Most of the device operation (such as mass storage) initiated from host > > (except HID) and USB wakeup aligned with host resume procedure. For BT > > device, usb-wakeup capability need to enable form btusc driver as a > > generic solution for multiple profile use case and required for USB remote > > wakeup (in-bus wakeup) while host is suspended. Also usb-wakeup feature > > need to enable/disable with HCI interface up and down. > > > > Signed-off-by: Sukumar Ghorai <sukumar.ghorai@xxxxxxxxx> > > Signed-off-by: Amit K Bag <amit.k.bag@xxxxxxxxx> Acked-by: Oliver Neukum <oneukum@xxxxxxxx> -- 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
