From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Date: Sat, 22 Nov 2014 13:48:15 +0000 (+0100)
Subject: ARM: 8218/1: warn if bad IRQ was scheduled
X-Git-Tag: v4.14-rc1~6315^2~1^2~8
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=44cb09c23f8e5838f24ef47d43dd2804b71b3a65;p=platform%2Fkernel%2Flinux-rpi.git

ARM: 8218/1: warn if bad IRQ was scheduled

If somebody causes an unexpected bad IRQ, this even will be unnoticed in
both dmesg and system logs. If the "bad" IRQ is stuck, the device will
just hang silently w/o reporting anything. Compare this to the generic
behaviour (from include/asm-generic/hardirq.h) which prints a message
with critical level. So to help everybody, include the same message into
ARM-specific ack_bad_irq().

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
---

diff --git a/arch/arm/include/asm/hw_irq.h b/arch/arm/include/asm/hw_irq.h
index a71b417..af79da4 100644
--- a/arch/arm/include/asm/hw_irq.h
+++ b/arch/arm/include/asm/hw_irq.h
@@ -8,6 +8,7 @@ static inline void ack_bad_irq(int irq)
 {
 	extern unsigned long irq_err_count;
 	irq_err_count++;
+	pr_crit("unexpected IRQ trap at vector %02x\n", irq);
 }
 
 void set_irq_flags(unsigned int irq, unsigned int flags);