Russell King <[EMAIL PROTECTED]> wrote: > I think the root of this issue is that you're thinking that the driver > uses this to dictate to the interrupt controller what it wants the > controller to program itself for. It's more a case that the driver is > saying "my device produces this kind of interrupt, please configure > the input appropriately."
Okay. Still, I'd like to see some handling for a mismatch - the case in which the driver says "my device can produce X" but X isn't available with that PIC/bus combination. Or maybe provide a way (if there isn't one already) for the driver to query the available trigger types. Some devices I've come across have configurable interrupt generators. David
