> Hey. I just wanted to pipe in that I had this problem for a short
> while as well. It boggled my mind.. doesn't spin_lock prevent two
> interrupt handlers from entering this function at the same time?
>
> irq_active is only referenced in this function, and it's subtracted
> at the end. I did
BUG_ON(isp1362_hcd->irq_active++);
1092:
1093:isp1362_write_reg16(isp1362_hcd, HCuPINTENB, 0);
It would appear that it is entering the interrupt handler twice for some
reason.
Should I be setting the IRQ falling/rising edge with set_irq_type?
--
Bluewater Systems Ltd
HCATLCURR [1e]
HCATLDTC [51]
HCATLDTCTO [52]
periodic size= 32
ISO:
--
Bluewater Systems Ltd - ARM Technology Solutions Centre
Andre Renaud Bluewater Systems Ltd
Phone: +64 3 3779127 (Aus 1 800 148 751)Level 17, 119 Armagh
nPWE instead of nWE as write strobe.
How are you connecting the ISP1362 up to the RDY signal on the PXA for
VLIO mode access?
--
Bluewater Systems Ltd - ARM Technology Solutions Centre
Andre Renaud Bluewater Systems Ltd
Phone: +64 3 3779127 (Aus 1 800 148 751)
On Wed, 2005-04-20 at 10:30 +0200, Lothar Wassmann wrote:
> > 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 write instructions complete before the
> actual write to the dev
Does anyone know if there has been much work recently on the OHCI-based
ISP1362 driver? I see that at http://www.karo-electronics.de/132.0.html
the last update was in November of last year, and from the mailing list
it looks as if the idea of basing them on the OHCI framework has died
off.
On an a
