Matthew Garrett wrote: > On Fri, Jun 26, 2009 at 03:13:13PM -0700, Kok, Auke wrote: > >> I'm all for actually giving people actually a chance to 'break' their system. >> having a keyboard break because someone used powertop isn't that bad: We >> find out >> that there is a bad keyboard out there first of all, something we would have >> missed completely. > > Heh. I'm fine with it being suggested in the sense of "Press this to > save some power but potentially break your system", but currently it's > something that can cause subtle breakage (many printers and scanners > will stop working) and users may not connect the two. > >> when does the kernel set 'power/autosuspend' to -1? > > Only if booted with usbcore.autosuspend=-1. Otherwise it implies that > the user or distribution has forcibly disabled it. > >> we can certainly 'blacklist' "input" devices, if there was an elegant way to >> detect whether a device is indeed such a thing from sysfs... > > Easiest is to look at the driver links for the interfaces in sysfs. That > ought to link to hid for input devices.
ok, I'll take a stab at that, powertop can use some love anyway. I'll propably remove any code that changes power/autosuspend for now, but I'll keep the code that sets power/level from "on" to "auto"... indeed I can readlink() the driver symlink, which then results in `usbhid` and allows me to blacklist the device. It'll be next week when I get to this, perhaps people can check out the svn version in a week or so and test. Auke _______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
