A few more qeustions, if I may: Right now we search for the device by going through /proc/bus/usb/, one device at a time, opening it, reading the device descriptor, and then either using or closing it. Does htis mean that we're needlessly resuming/suspending all the devices? How does lsusb do it? Should we be querying the device via sysfs instead even though it means a lot more open/read/close system calls?
Is it guaranteed that the current value in .../power/autosuspend will have been read when the close() returns or might the final stages of closing the device occur somewhat later? In other words, is there a possibility that we'll be defeating ourselves by restoring the original value right after the close()? Is there any kind of damping in the system to prevent problems/overload if a device is opened/closed too often too close together? -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. http://FamilyRadio.com/ | http://Mielke.cc/bible/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
