From: NIIBE Y. <gn...@ch...> - 2000-09-08 02:33:38
|
Takashi says there's problem with irq_imask interrupt when probe_irq is used. When shutdown of the irq is called, IMASK has been changed which raises the IMASK. Irq_imask is different beast, the default state is all enabled, so here's the patch. 2000-09-08 NIIBE Yutaka <gn...@m1...> * arch/sh/kernel/irq_imask.c (startup_imask_irq, shutdown_imask_irq): Don't do anything. When used with proble_irq, interrupt may be masked. NOTE: For IMASK, default is "all enabled". =================================================================== RCS file: /cvsroot/linuxsh/kernel/arch/sh/kernel/irq_imask.c,v retrieving revision 1.9 diff -u -r1.9 irq_imask.c --- arch/sh/kernel/irq_imask.c 2000/07/31 12:26:21 1.9 +++ arch/sh/kernel/irq_imask.c 2000/09/07 10:33:17 @@ -41,7 +41,7 @@ static unsigned int startup_imask_irq(unsigned int irq) { - enable_imask_irq(irq); + /* Nothing to do */ return 0; /* never anything pending */ } @@ -103,12 +103,12 @@ static void shutdown_imask_irq(unsigned int irq) { - disable_imask_irq(irq); + /* Nothing to do */ } void make_imask_irq(unsigned int irq) { disable_irq_nosync(irq); irq_desc[irq].handler = &imask_irq_type; - enable_irq(irq); + disable_imask_irq(irq); } |