On Sun, Jun 07, 2009 at 11:03:48PM -0400, Alan Stern wrote: > There's no mechanism for this. It many environments it couldn't work, > because the decision about whether to enable autosuspend is made when > the device is first created (i.e., when the creation uevent is > received), whereas driver binding doesn't occur until later. There's a lot of power management situations where you don't end up with the optimal power configuration until a driver's bound. It's certainly possible to do this in userspace, but if we know that the hardware supported by a given driver will always work then it seems reasonable to have it whitelist autosuspend on that device. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
