On Thu, Oct 13, 2011 at 09:38:22AM +0200, Oliver Neukum wrote: > Hi, > > up to now we have pushed the issue of activating autosuspend to user space. > Presumably to be solved with udev and large white and black lists. Doing this > in practice has turned out very tedious. Doing it for device classes with > exceptions in the form of black lists has turned out outright difficult because > a device may have interfaces belonging to several classes, which may be treated > differently. > So in my opinion this needs a solution in user space with a little more sophistication. > I therefore have written this tool which includes class and id based solutions. > > It defines four categories with respect to autosuspend into which classes > can be divided. > > a - always autosuspend > b - autosuspend preferred > c - neutral > d - never autosuspend > > For a device to be autosuspended it must have at least one category a > or category b interface and must not have a category d interface. What happens > if a meets d I haven't yet decided. > > Solutions based on IDs always override the decision based on classes. > > And because we've never solved the configuration issue, this tools also allows > setting configurations based on IDs. > The configuration files are based on glib, so they are relatively easy to manipulate > with tools and are nicely readable to humans. > > It is currently useful to me but I'd still like to add some features. > > - symbolic class names > - decisions on autosuspend based on subclasses and maybe protocols > Do you consider it useful? It looks nice, could you provide a man page, or some type of documentation that shows how it is to be used? Would this be good to add to the usbutils package? thanks, greg k-h -- 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
