Hi Kevin, On Wed, 2 May 2012, Kevin Hilman wrote: > >From 22726db6fc514cc5110db43fdf05d5afda8e4a59 Mon Sep 17 00:00:00 2001 > From: Kevin Hilman <khilman@xxxxxx> > Date: Tue, 1 May 2012 07:06:42 -0700 > Subject: [PATCH] ARM: OMAP3: PM: leave PRCM interrupts disabled until > explicitly enabled. > > By default, request_irq() will auto-enable the requested IRQ. > > For PRCM interrupts, we may want to avoid that until the PM core code > is fully ready to handle the interrupts. This is particularily true > for IO pad interrupts on OMAP3, which are shared between the hwmod > core and the PRM core. > > In order to avoid PRCM IO-chain interrupts until the PM core is ready > to handle them, ready, set the IRQ_NOAUTOEN flag for the PRCM IO-chain > interrupt, which means it will remain disabled after request_irq(). > > Then, explicitly enable the PRCM interrupts after the request_irq() in > the PM core (but not in the hwmod core.) > > Special thanks to Tero Kristo for suggesting to isolate the fix to > only the IO-chain interrupt on OMAP3 instead of all PRCM interrupts. > > Tested-by: Afzal Mohammed <afzal@xxxxxx> > Acked-by: Tero Kristo <t-kristo@xxxxxx> > Cc: Paul Walmsley <paul@xxxxxxxxx> > Signed-off-by: Kevin Hilman <khilman@xxxxxx> Acked-by: Paul Walmsley <paul@xxxxxxxxx> If for some reason it doesn't get in for 3.5, let me know and I'll queue with the other IO chain patches for 3.6 as we discussed. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
