On Wed, 27 Apr 2005, David Brownell wrote: > > > Right, but if usbcore says "activate the root hub" then port change IRQs > > > can come immediately. And then how can the HCD tell usbcore to collect > > > that status, if hasn't registeed the root hub? > > > > It can't. Or with patch as478b, it can by calling usb_hcd_poll_rh_status > > -- but that won't accomplish anything (other than invoking the hub_status > > callback) until the root hub has been registered. So what? Does this > > cause any kind of problem? > > Lost events are to be avoided...
Agreed in general, but in this particular case it won't hurt. As soon as the root hub is registered, khubd will scan all its ports. So the events won't be lost forever. > > So this won't matter once usb_hcd_root_hub_lost_power is written, right? > > Shouldn't, if it's done right. But you were asking about why it's > done that way _now_, and that's the answer. Okay, I just wanted to make sure. > > From the USB specification, table 11-13 (p.418): > > > > 6 bHubContrCurrent 1 Maximum current requirements of the Hub > > Controller > > electronics in mA. > > I wasn't talking about the controller itself ... I was talking about its > power budget. Different concepts. And irrelevant now that the power_budget patch is written. Alan Stern ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
