Message ID | 56B34EB7.4080005@ti.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On 04/02/16 13:14, Grygorii Strashko wrote: > Hi Sudeep, > > On 02/01/2016 08:28 PM, Sudeep Holla wrote: >> The IRQF_NO_SUSPEND flag is used to identify the interrupts that should >> be left enabled so as to allow them to work as expected during the >> suspend-resume cycle, but doesn't guarantee that it will wake the system >> from a suspended state, enable_irq_wake is recommended to be used for >> the wakeup. >> >> This patch removes the use of IRQF_NO_SUSPEND flags replacing it with >> enable_irq_wake instead. > > And sorry for delayed reply - I've spent some time investigating it, but > It was during Christmas holidays and finally I lost track of it :) > That's fine, usually that's the case in general will all of us :) [..] > > Another option is to convert omap_prcm_irq_handler to the generic handler > (now chained) and, probably, make it threaded and all cascaded IRQs as > nested threaded (this is just a theory). > Since I don't have any knowledge of OMAP, I will completely depend on your for anything OMAP specific. > I'll be on business trip next two weeks and will not be able to help more with it > Sorry. > No problem, let me know once you get a chance to try out things at your end.
diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c index 58920bc..a0f8265 100644 --- a/arch/arm/mach-omap2/pm.c +++ b/arch/arm/mach-omap2/pm.c @@ -221,8 +221,7 @@ static int omap_pm_enter(suspend_state_t suspend_state) static int omap_pm_begin(suspend_state_t state) { cpu_idle_poll_ctrl(true); - if (cpu_is_omap34xx()) - omap_prcm_irq_prepare(); + omap_prcm_irq_prepare(); return 0; } @@ -233,8 +232,7 @@ static void omap_pm_end(void) static void omap_pm_finish(void) { - if (cpu_is_omap34xx()) - omap_prcm_irq_complete(); + omap_prcm_irq_complete(); } Another option is to convert omap_prcm_irq_handler to the generic handler