But the host side can't track SUSPENDED reasonably anyway, and does not need to. It's the other states that are interesting. I agree that if we wanted to do anything with SUSPENDED it'd need thought.
Hm, I thought that if you suspend a device, that the host knows about it. But it's been a long time since I had to worry about device states, when writing USB firmware. All I remember is having long arguments with people about the whole SUSPENDED thing, and in the end, I don't think anyone even uses it...
So long as the bus has SOF's going over it, I don't think suspend will kick in. Host controllers can suspend if there's no traffic or if the host as a whole is suspending (like "apm -s").
No, the spec doesn't say that ATTACHED is when the device is removed from the system. Section 9.1.1.1 says: The state of a USB device when it is detached from the USB is not defined by this specification.
So I say we add NOTATTACHED, as we do care about that state.
Still doesn't seem like a different state to me... what's the difference in behavior? But if that's really what you want to see, I'll add it anyway, it's simple enough.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
