On Fri, May 18, 2012 at 12:46 PM, Mohammed, Afzal <af...@ti.com> wrote: > Hi Santosh, > > On Fri, May 18, 2012 at 12:33:16, Shilimkar, Santosh wrote: >> + Afzal who has been doing quite a bit of GMPC work recently. >> >> On Fri, May 18, 2012 at 10:13 AM, Ming Lei <ming....@canonical.com> wrote: >> > The IRQ52 on OMAP2+ is not a shared interrupt line. If IRQF_SHARED >> > is passed to request_irq and dev_id is set as NULL, request_irq will >> > return -EINVAL. >> > >> GPMC IRQ line can shared between the multiple devices you >> connect on it. > : >> Are you sure it fails ? >> I just tried booting OMAP4 with 3.4-rc4 and don't see the irq >> failure error message. What I am missing ? > > Issue happens on l-o master, this was mentioned in [1], now I feel > right solution is to keep dev-id. > Thanks for the reference. removing SHARED flag is not solution and yes, you might have to keep the dev-id if that was the issue.
Regards Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
