3.2.54-rc1 review patch. If anyone has any objections, please let me know.
------------------ From: Laxman Dewangan <ldewan...@nvidia.com> commit ac01810c9d2814238f08a227062e66a35a0e1ea2 upstream. When the system enters suspend, it disables all interrupts in suspend_device_irqs(), including the interrupts marked EARLY_RESUME. On the resume side things are different. The EARLY_RESUME interrupts are reenabled in sys_core_ops->resume and the non EARLY_RESUME interrupts are reenabled in the normal system resume path. When suspend_noirq() failed or suspend is aborted for any other reason, we might omit the resume side call to sys_core_ops->resume() and therefor the interrupts marked EARLY_RESUME are not reenabled and stay disabled forever. To solve this, enable all irqs unconditionally in irq_resume() regardless whether interrupts marked EARLY_RESUMEhave been already enabled or not. This might try to reenable already enabled interrupts in the non failure case, but the only affected platform is XEN and it has been confirmed that it does not cause any side effects. [ tglx: Massaged changelog. ] Signed-off-by: Laxman Dewangan <ldewan...@nvidia.com> Acked-by-and-tested-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com> Acked-by: Heiko Stuebner <he...@sntech.de> Reviewed-by: Pavel Machek <pa...@ucw.cz> Cc: <ian.campb...@citrix.com> Cc: <r...@rjwysocki.net> Cc: <len.br...@intel.com> Cc: <gre...@linuxfoundation.org> Link: http://lkml.kernel.org/r/1385388587-16442-1-git-send-email-ldewan...@nvidia.com Signed-off-by: Thomas Gleixner <t...@linutronix.de> Signed-off-by: Ben Hutchings <b...@decadent.org.uk> --- kernel/irq/pm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/kernel/irq/pm.c +++ b/kernel/irq/pm.c @@ -50,7 +50,7 @@ static void resume_irqs(bool want_early) bool is_early = desc->action && desc->action->flags & IRQF_EARLY_RESUME; - if (is_early != want_early) + if (!is_early && want_early) continue; raw_spin_lock_irqsave(&desc->lock, flags); -- 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/
