On Tuesday 23 November 2004 14:15, Alan Stern wrote: > It's not a question of using timers or anything else. If wakeup_enabled > isn't set then the HCD _must not_ allow wakeup/resume signalling in any > form. Regardless of whether it is able to. That's the whole point of the > wakeup_enabled flag, right?
I'd describe "wakeup_enabled" as "allow wakeup", rather than "!wakeup_enabled" as "... also treat wakeup as error". When devices misbehave, their parent devices will still receive the wakeup signaling. I suppose the khubd could just not resume devices when "!wakeup_enabled", but that still wouldn't be a "must not". > Without the possibility of resume signalling, we won't want to > autosuspend the root hub. There's no argument about that, I hope. Without the possibility of resume signaling, no USB device will really be suspended ... so whatever an HCD does to reduce power consumption won't be "autosuspend", right? Drivers need to be free to (transparently) reduce power usage at any time. I've called what OHCI does now "autosuspend", which expects IRQs to work (and tolerates root hub timer polling) ... usbcore has no need to care about that state. - Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
