On Monday 29 May 2006 7:12 am, [EMAIL PROTECTED] wrote: > According to OHCI specification RWC bit is to indicate whether the > controller supports remote wakeup or not and this bit is set by the > system firmware at the time of POST. But this bit is set in > ohci_bus_resume depending on hcd->can_wakeup flag.
Uhm, that flag has been removed. And I don't see any code in the current version of that routine to set RWC ... or even to test the driver model flag which replaced that root hub flag. > But I don't find > where this can_wakeup flag is initialised. Platform setup code, or sometimes the bus glue. See <linux/pm.h>... > According to OHCI specification if RWE bit is set and RD bit of > interrupt register is set then only a remote wakeup is signaled to the > host system. Does this mean that if both the bits are set then the > system can resume by remote wakeup? > Or if I put it alternativly, if my bus is suspended selectively and RWE > bit is not set then does RD interrupt can wakeup the bus ? Right now the OHCI driver is coded to expect that remote wakeup requires both RWE and RD, although there's a patch pending in that area (associated with driving the root hub primarily by IRQ). - Dave ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
