Hi Alan, Back in October, there was a discussion about USB storage autosuspend. The general consensus seemed to be that we should convert the USB and SCSI subsystems over to the runtime PM framework and then implement USB storage autosuspend, instead of doing an autosuspend hack with layering violations. I'm being nudged to do such a hack, because a lot of netbooks have SD card readers that are empty most of the time. I would rather not do such a hack if a better solution exists. What are your plans with USB storage autosuspend? On Fri, Jan 08, 2010 at 12:55:54PM -0500, Alan Stern wrote: > The following series culminates in a patch which replaces the USB > autosuspend implementation with the runtime PM framework. Earlier > patches make a bunch of simple changes intended to ease the path, such > as removing uses of the USB device-pm mutex, changing the way the > various autosuspend-disable and -enable schemes work, and even just > rearranging code to make it look better. > > The individual patch descriptions speak for themselves, except perhaps > for the last which doesn't go into very much detail considering the > patch's size. If anybody is interested in more information about how > the runtime PM framework is used, I'll be happy to explain. I'm interested in how the runtime PM framework is used. Perhaps I'll read over your last patch and ask questions? Are there any other information, resources, or other email threads I should also be looking at? I saw Rafael's thread on Jan 24th, but haven't had a chance to read it yet. 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
