On Tue, 2017-10-03 at 21:00 +0800, wg...@china.com wrote: > Because, as long as it gets enumerated as a USB device, which I > > suspect > > is what should happen here, it would be covered. > > > Yes, the bluetooth dongle is connected to a USB port on my laptop, > and I have noticed the "hub usbhid usb-storage" is list in the > AUTOSUSPEND_RUNTIME_DEVTYPE_BLACKLIST. But the bluetooth power saving > is not be disabled unless I add the device id of bluetooth in the > AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST. >
Hmmm.. > > Can you share your runtime-pm.conf ? > > > Yes, my runtime-pm.conf is like this, and the device id 8087:0a2b is > the bluetooth device id in my laptop. > > # The list of Device IDs that should not use autosuspend. Use system > commands or > # look into sysfs to find out the IDs of your devices. > # Example: AUTOSUSPEND_DEVID_BLACKLIST="046d:c025 0123:abcd" > AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST="8087:0a2b" > > # The list of device driver types that should not use > autosuspend. The driver > # type is given by "DRIVER=..." in a device's uevent file. > # Example: AUTOSUSPEND_DEVID_BLACKLIST="usbhid usb-storage" > AUTOSUSPEND_RUNTIME_DEVTYPE_BLACKLIST="hub usbhid usb-storage" > Thanks for the information. My guess, so far from what you have mentioned, is that this device type is not getting classified as a USB class device. But I still think that is very very weird, given that the BT dongle connects to the USB port. Can you run in debug mode, with only the runtime-pm module having debugging enabled ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part