Hi,
> So, I ignored the error with the CLKRDY pin, but now I'm getting
> two problems:
> 1a. I'm getting failed memory checks
> 1b. I'm triggering the _WARN_ON statements regarding HCuPINT_EOT at
> the end of write_buffer (which I'm assuming is the cause of 1a)
>
Yes. This is a sure sign that wri
Hi,
> Hi. I'm having some trouble with your driver, and there's parts I
> don't understand. The one I'm asking about this time, is: Where is
> XFERCTR being set? The below code snippet mentions assuming it's
> set up, but I can't find the code that actually sets it up!
>
> // use readsw/writes
On Tue, 2005-04-19 at 14:08 -0700, Michael wrote:
> Yes, that's interesting. On the ISP1362, the H_SUSPEND line needs
> to be pulled up, with a low strobe to wake it up.
especially interesting since the isp1160 requires that it be low and
strobed high:
H_WAKEUP 40 I HC wake-up input; generates a
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
On Wed, 2005-04-20 at 13:32 +0300, Olav Kongas wrote:
> 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
Sorry to trouble you all. I've had a look at the USB docs in the
kernel but I can't find the answer to my problem. I'm developing a mass
storage device and manage to crash the USB 2/3 times a day. At the
moment I'm rebooting the entire PC to recover. Is there a better method
of just restarting the
On Wed, 20 Apr 2005, Ian Campbell wrote:
> On Wed, 2005-04-20 at 13:32 +0300, Olav Kongas wrote:
> > 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
> > RemoteWakeupConnec
Am Mittwoch, 20. April 2005 13:11 schrieb Bill Adair:
> Sorry to trouble you all. I've had a look at the USB docs in the
> kernel but I can't find the answer to my problem. I'm developing a mass
> storage device and manage to crash the USB 2/3 times a day. At the
> moment I'm rebooting the entire P
On Wednesday 20 April 2005 12.32, Olav Kongas wrote:
> I think I'll amend the CLKRDY-triggered error message in the
> driver to mention H_WAKEUP as a possible cause.
That was my problem, with the GPIO attached to H_WAKEUP initialized
to 0 the test succeeds, thanks Ian. So yes, mentioning this in
On Tuesday 19 April 2005 7:12 pm, mike lee wrote:
> Hi all
> I am now writing a gadget controller driver, but face some problem
> when the driver still in enumeration.
> Here is what i get from the host, it is very strange that my hardware
> only support 2 configuration, so don't know why can't
/* shutdown our bulk reads and writes */
spin_lock_irqsave(&info->lock, flags);
list_for_each_safe(tmp, tmp2, &info->rx_urbs_submitted) {
wrap = list_entry(tmp, struct whiteheat_urb_wrap, list);
urb = wrap->urb;
usb_kill_urb(ur
On Wed, Apr 20, 2005 at 08:26:29PM +0200, Oliver Neukum wrote:
> /* shutdown our bulk reads and writes */
> spin_lock_irqsave(&info->lock, flags);
> list_for_each_safe(tmp, tmp2, &info->rx_urbs_submitted) {
> wrap = list_entry(tmp, struct whiteheat_urb_wrap, list);
>
12 matches
Mail list logo
