...
PC104 interrupts for vipers at a2, a6 and c20 are OK.
USB
...
Interrupts
The viper kernel has a patch to use an assembler delay function for the isp116x, and not the kernel ndelay() function. Don't think It is not known whether this is related thoughto the high interrupt rate. An incorrect delay may result in the USB interface completely failing.
The driver code that sets up the interrupt, uses two configuration values, int_act_high and int_edge_triggered, which are used to configure the interface:
| Code Block |
|---|
if (board->int_act_high)
val |= HCHWCFG_INT_POL;
if (board->int_edge_triggered)
val |= HCHWCFG_INT_TRIGGER;
|
The current isp116x , driver is configured for level triggered (int_edge_triggered=0, default) and active high (int_act-high=1) interrupts. However, the setting for the corresponding GPIO interrupt is IORESOURCE_IRQ_HIGHEDGE. Maybe that's a problemIn testing after the project, make those consistent, and test with one or two vipers.
