Oliver, Unfortunately, autosuspend of btusb does not seem to work on my notebook with 2.6.34-rc3: 1) powertop -d reports: 100.0% USB device 7-1 : BCM92045NMD (Broadcom Corp) 100.0% USB device usb7 : UHCI Host Controller (Linux 2.6.34-rc3 uhci_hcd) 2) lsusb: Bus 007 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 3) autosuspend settings: /sys/module/usbcore/parameters/autosuspend : 2 /sys/bus/usb/devices/7-1/power/level : auto /sys/bus/usb/devices/usb7/power/level : auto 4) hciconfig hci0: Type: USB BD Address: 00:XX:XX:XX:XX:XE ACL MTU: 1017:8 SCO MTU: 64:8 DOWN RX bytes:971 acl:0 sco:0 events:28 errors:0 TX bytes:364 acl:0 sco:0 commands:28 errors:0 5) All userspace tools suspectible of connecting to btusb (bluetoothd, bluez-applet, even something called obex-data) are stopped, killed or whatever. 6) rmmod btusb leads to: 0,0% USB Gerät 7-1 : BCM92045NMD (Broadcom Corp) 0,0% USB Gerät usb7 : UHCI Host Controller (Linux 2.6.34-rc3 uhci_hcd) 7) A bit off topic: might btusb be one of the drivers which could autoenable autosuspend? Best, Dominik -- 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
