On Sun, 24 Apr 2005, Alan Stern wrote: > I tried this out with an OHCI controller and it seemed to work. I'll post > the patches tomorrow. > > But I encountered a problem with resume-detect interrupt handling. > Probably this has nothing to do my changes and was present all along, but > I haven't tested the vanilla driver to make sure. I'll do that next.
FYI Yes, the vanilla driver behaved the same way. This morning I tried testing an EHCI controller. Its behavior was even more puzzling. After I suspended the root hub and its interface, plugging or unplugging a device had no effect at all! The driver didn't wake up and the port change wasn't recognized until I resumed the root hub by hand. This was on a regular Intel ICH4 motherboard: 00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI]) Subsystem: Intel Corp.: Unknown device 5247 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Interrupt: pin D routed to IRQ 10 Region 0: Memory at ffa7fc00 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Debug port Alan Stern ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel