On Fri, 2 Nov 2012 13:47:25 -0500 Matt Schulte <matts@xxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Nov 1, 2012 at 5:26 PM, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: > >> Hello, the next question that I have is how to handle the interrupts > >> on this UART. It has a more complex interrupt scheme than a > >> traditional 8250 UART. There is a global ISR register that tells you > >> which port had the interrupt and then there is another set of > >> registers that hold the actual interrupts. > > > > port->handle_irq is half of what you need, but you probably need to be > > able to hook serial8250_interruot and provide your own alternative. Given > > you don't need the irq chain handling either probably the bit that wants > > to be hookable is the calls to serial_link_irq_chain and > > serial_unlink_irq_chain in the startup/shutdown methods. > > > > In yor case all that and all the irq scanning the chain becomes a simple > > read of the port and call of the handlers (serial8250_handlee_irq(port, > > iir) > > To be clear, I shouldn't put a custom irq handler inside 8250.c, correct? > > I would want to do something along the vein of 8250_dw.c with a custom > probe and a custome handle_irq? That's my first guess - there is an awful lot of stuff you simply don't need in this situation. -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
