I've been testing a 3G modem that uses the option driver in 2.6.37, and we noticed that the device wasn't going into autosuspend. Upon further investigation, we found that remote wakeup is disabled by default, and the option driver will only suspend the device between transmissions if remote wakeup is enabled by userspace. Is there a reason remote wakeup is disabled by default? Is there a history of devices that use the option driver having issues with auto-suspend? It seems like if the USB device advertises remote wakeup and the device is self-powered, then we should turn on remote wakeup by default. Sarah Sharp -- 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