> Is the interrupt triggered forever by the isp1161a1 even after
> outplugging the storage-device?
If there are INT urbs submitted to the driver then SOF
interrupt is enabled and ATL interrupt is disabled.
Otherwise (which includes control and/or bulk urbs or no
urbs at all) the SOF interrupt is disabled and ATL is
enabled. Therefore, soon after umplugging you shouldn't see
interrupts as all the submitted urbs should be dequeued.
> irqstat: 0x7
> isp116x->irqenb: 0x12 ret value: 0x1
>
> irqstat = isp116x_read_reg16(isp116x, HCuPINT);
> printk("irqstat: 0x%x\n", irqstat);
> isp116x_write_reg16(isp116x, HCuPINT, ~0);
>
> and:
>
> spin_unlock(&isp116x->lock);
> printk("isp116x->irqenb: 0x%x ret value: 0x%x\n", isp116x->irqenb, ret);
> return ret;
These printouts look ok.
> > You could compare the register dumps from the two drivers as
> > well as the irq pin settings on the processor.
>
> The "old" isp1362/isp116x driver acts in a similair way, but the
> interrupt seems to be triggered with mask 0x33 and int status 0x10
> and 0x11 alternating. Seems to be all ok then, since SOFInt comes every
> 1ms...
Still, could you post isp116x chip's register dumps obtained
just after chip initialization for both Lothar's and my
driver. In my one, you should get it if you uncomment the
DEBUG macro at the beginning of the isp116x-hcd.c.
Olav
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
