> You should probably clear the 'int_edge_triggered' flag in the > platform_data to make the chip assert its interrupt output until the > interrupt has been acknowledged to the chip, since the 160ns pulse > that the chip generates in 'edge triggered mode' may be too short to > be detected by the CPU (which is e.g. true for PXA2xx).
Thanks for this clearing int_edge_triggered has made the interrupts
appear, but unfortunately now I hit a 'BUG_ON' in isp1362_irq,
1089: spin_lock(&isp1362_hcd->lock);
1090:
1091: 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 - ARM Technology Solutions Centre
Andre Renaud Bluewater Systems Ltd
Phone: +64 3 3779127 (Aus 1 800 148 751) Level 17, 119 Armagh St
Fax: +64 3 3779135 PO Box 13889
Email: [EMAIL PROTECTED] Christchurch
Web: http://www.bluewatersys.com New Zealand
signature.asc
Description: This is a digitally signed message part
