Dmitry Eremin-Solenikov <dbaryshkov@xxxxxxxxx> writes: > 2014-11-22 16:56 GMT+03:00 Robert Jarzmik <robert.jarzmik@xxxxxxx>: >> Robert Jarzmik <robert.jarzmik@xxxxxxx> writes: >>> Okay, now my ADSL line is repaired, thank you Mr farmer "I drive a tractor but I >>> don't care about telephone posts", I'll fetch your changes and make a >>> test. Let's say I schedule this for saturday. >> >> Removed people from the list for the tests aspect. >> >> Well, my lubbock board seem to raise several interrupts in the linux kernel, all >> the LUBBOCK_IRQ interrupts multiplexed on GPIO0 actually, amongst which are the >> 2 interrupts for the UDC. Arg, what I meant to write was "seem to *never* raise several interrupts". > This looks normal - GPIO0 is connected to an interrupt pin of the CPLD. > lubbock_init_irq function should be setting up a chained handler for the GPIO0. > And that chained handler (lubbock_irq_handler) should further decode which > IRQ bit is set. Do you see the handler being called? Can you print the (pending) > variable in the handler? lubbock_irq_handler() is never called. pxa_gpio_demux_handler() is never called. => this is the one worrying me most. And as the lubbock_irq_handler() is never called there is not point in printing that yet, first should be finding out why on earth the gpio demux is not getting called. Cheers. -- Robert -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
