Hi Andrew, My platform/board is ATCA carrier card which is getting interface to I/O card. The I/O card is hot-pluggable or Jack-in or Jack out. Also I/O card consists of hot-plugable SFP interface. These events are triggered using GPIO's
So the events the carrier card recieves are 1) If I/O card is either Jacked-in or Jacked-out ,respective GPIO pin-x triggers an event 2) If SFP is pushed into I/O card the respective GPIO pin-y triggers an event. Another observation about "irq: Cannot allocate irq_descs @ IRQ47/79/111". This is warning & irq_descs are already allocated , the overall initialization/probe function doesn't get effected. mvebu_gpio_irq_handler is only called if I register a another handler at irq=82/83/84/85/87/88/89/90/92. I am registering this handler using minimal kernel module. My understanding of Linux IRQ/interrupt mechanism is limited to request_irq, but registering domain & then IRQ is bit not clear. Regards Raghu On Wed, Aug 5, 2015 at 9:51 PM, Andrew Lunn <and...@lunn.ch> wrote: > On Wed, Aug 05, 2015 at 08:31:27PM +0530, raghu MG wrote: >> Hi Andrew, >> >> The issue I found was irq_alloc_descs is called twice >> 1st time inside mvebu_gpio_probe & 2nd time inside irq_domain_add_simple. > > So i'm somewhat confused. I just tested on my Kirkwood and 370 > platforms, and an Armada XP WRT1900AC using 4.2.0-rc5, all which use > the same gpio driver. > > They boot fine, the gpio driver is loaded, and the interrupt for the > gpio connected to a button are listed in /proc/interrupts. The > gpio-key driver is also able to use the gpio and the input-events > program does show events when i press the button. > > So what is different with your platform? > > Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/