genirq: Don't suspend nested_thread irqs over system suspend

Nested IRQs can only fire when the parent irq fires. So when the
parent is suspended, there is no need to suspend the child irq.

Suspending nested irqs can cause a problem is they are suspended or
resumed in the wrong order. If an interrupt fires while the parent is
active but the child is suspended, then the interrupt will not be
acknowledged properly and so an interrupt storm can result. This is
particularly likely if the parent is resumed before the child, and the
interrupt was raised during suspend.

Ensuring correct ordering would be possible, but it is simpler to just
never suspend nested interrupts.

Signed-off-by: NeilBrown <[e-mail]>
Cc: GTA04 owners <[e-mail]>
Cc: Kalle Jokiniemi <[e-mail]>
Acked-by: Peter Zijlstra <[e-mail]>
Cc: Rafael J. Wysocki <[e-mail]>
Link: http://lkml.kernel.org/r/[e-mail]
Signed-off-by: Thomas Gleixner <[e-mail]>

kernel/irq/pm.c

···
 		unsigned long flags;
 		bool sync;
 
+		if (irq_settings_is_nested_thread(desc))
+			continue;
 		raw_spin_lock_irqsave(&desc->lock, flags);
 		sync = suspend_device_irq(desc, irq);
 		raw_spin_unlock_irqrestore(&desc->lock, flags);
···
 			desc->action->flags & IRQF_EARLY_RESUME;
 
 		if (!is_early && want_early)
+			continue;
+		if (irq_settings_is_nested_thread(desc))
 			continue;
 
 		raw_spin_lock_irqsave(&desc->lock, flags);