blob: bac94ee6bc90bd5e259ad95c6ea18d5d38896c9d [file] [log] [blame]
Mikael Starvik51533b62005-07-27 11:44:44 -07001#ifndef _ASM_ARCH_IRQ_H
2#define _ASM_ARCH_IRQ_H
3
Mikael Starvik51533b62005-07-27 11:44:44 -07004#include "hwregs/intr_vect.h"
5
6/* Number of non-cpu interrupts. */
7#define NR_IRQS 0x50 /* Exceptions + IRQs */
8#define NR_REAL_IRQS 0x20 /* IRQs */
9#define FIRST_IRQ 0x31 /* Exception number for first IRQ */
10
11#ifndef __ASSEMBLY__
12/* Global IRQ vector. */
13typedef void (*irqvectptr)(void);
14
15struct etrax_interrupt_vector {
16 irqvectptr v[256];
17};
18
19extern struct etrax_interrupt_vector *etrax_irv; /* head.S */
20
21void mask_irq(int irq);
22void unmask_irq(int irq);
23
24void set_exception_vector(int n, irqvectptr addr);
25
26/* Save registers so that they match pt_regs. */
27#define SAVE_ALL \
28 "subq 12,$sp\n\t" \
29 "move $erp,[$sp]\n\t" \
30 "subq 4,$sp\n\t" \
31 "move $srp,[$sp]\n\t" \
32 "subq 4,$sp\n\t" \
33 "move $ccs,[$sp]\n\t" \
34 "subq 4,$sp\n\t" \
35 "move $spc,[$sp]\n\t" \
36 "subq 4,$sp\n\t" \
37 "move $mof,[$sp]\n\t" \
38 "subq 4,$sp\n\t" \
39 "move $srs,[$sp]\n\t" \
40 "subq 4,$sp\n\t" \
41 "move.d $acr,[$sp]\n\t" \
42 "subq 14*4,$sp\n\t" \
43 "movem $r13,[$sp]\n\t" \
44 "subq 4,$sp\n\t" \
45 "move.d $r10,[$sp]\n"
46
47#define STR2(x) #x
48#define STR(x) STR2(x)
49
50#define IRQ_NAME2(nr) nr##_interrupt(void)
51#define IRQ_NAME(nr) IRQ_NAME2(IRQ##nr)
52
53/*
54 * The reason for setting the S-bit when debugging the kernel is that we want
55 * hardware breakpoints to remain active while we are in an exception handler.
56 * Note that we cannot simply copy S1, since we may come here from user-space,
57 * or any context where the S-bit wasn't set.
58 */
59#ifdef CONFIG_ETRAX_KGDB
60#define KGDB_FIXUP \
61 "move $ccs, $r10\n\t" \
62 "or.d (1<<9), $r10\n\t" \
63 "move $r10, $ccs\n\t"
64#else
65#define KGDB_FIXUP ""
66#endif
67
68/*
69 * Make sure the causing IRQ is blocked, then call do_IRQ. After that, unblock
70 * and jump to ret_from_intr which is found in entry.S.
71 *
72 * The reason for blocking the IRQ is to allow an sti() before the handler,
73 * which will acknowledge the interrupt, is run. The actual blocking is made
74 * by crisv32_do_IRQ.
75 */
76#define BUILD_IRQ(nr, mask) \
77void IRQ_NAME(nr); \
78__asm__ ( \
79 ".text\n\t" \
80 "IRQ" #nr "_interrupt:\n\t" \
81 SAVE_ALL \
82 KGDB_FIXUP \
83 "move.d "#nr",$r10\n\t" \
84 "move.d $sp,$r12\n\t" \
85 "jsr crisv32_do_IRQ\n\t" \
86 "moveq 1, $r11\n\t" \
87 "jump ret_from_intr\n\t" \
88 "nop\n\t");
89/*
90 * This is subtle. The timer interrupt is crucial and it should not be disabled
91 * for too long. However, if it had been a normal interrupt as per BUILD_IRQ, it
92 * would have been BLOCK'ed, and then softirq's are run before we return here to
93 * UNBLOCK. If the softirq's take too much time to run, the timer irq won't run
94 * and the watchdog will kill us.
95 *
96 * Furthermore, if a lot of other irq's occur before we return here, the
97 * multiple_irq handler is run and it prioritizes the timer interrupt. However
98 * if we had BLOCK'edit here, we would not get the multiple_irq at all.
99 *
100 * The non-blocking here is based on the knowledge that the timer interrupt is
Thomas Gleixneraa7135f2006-07-01 19:29:14 -0700101 * registred as a fast interrupt (IRQF_DISABLED) so that we _know_ there will not
Mikael Starvik51533b62005-07-27 11:44:44 -0700102 * be an sti() before the timer irq handler is run to acknowledge the interrupt.
103 */
104#define BUILD_TIMER_IRQ(nr, mask) \
105void IRQ_NAME(nr); \
106__asm__ ( \
107 ".text\n\t" \
108 "IRQ" #nr "_interrupt:\n\t" \
109 SAVE_ALL \
110 KGDB_FIXUP \
111 "move.d "#nr",$r10\n\t" \
112 "move.d $sp,$r12\n\t" \
113 "jsr crisv32_do_IRQ\n\t" \
114 "moveq 0,$r11\n\t" \
115 "jump ret_from_intr\n\t" \
116 "nop\n\t");
117
118#endif /* __ASSEMBLY__ */
119#endif /* _ASM_ARCH_IRQ_H */