On Tue, 19 Apr 2005, Robin Farine wrote:
> On Tuesday 19 April 2005 15.52, Ian Campbell wrote: > > > I was seeing this problem on a PXA255 with an isp1160. It went > > away when I corrected the H_WAKEUP pin to be pulled in the right > > direction, I can't remember if it needs to be pulled up or down > > but it needs to be in the state that doesn't cause a wakeup. Ian, thanks for this info. > Aha, good point. This pin is connected to a GPIO which I initialize > to a '1' so that must be it. Unfortunately, I do not have the > hardware at hand to verify that initializing it to zero fixes the > CLKRDY polling problem on this platform. On our platform here, the H_WAKEUP has always been pulled low and I haven't seen a problem with CLKRDY. The driver does not support wakeups through H_WAKEUP (the RemoteWakeupConnected bit = 0 in HcControl), because it is not needed as the wakeup via sysfs works. I think I'll amend the CLKRDY-triggered error message in the driver to mention H_WAKEUP as a possible cause. Olav ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
