|
|
|
|
#ifndef __ASM_ARM_IRQ_H
|
|
|
|
|
#define __ASM_ARM_IRQ_H
|
|
|
|
|
|
|
|
|
|
#include <asm/arch/irqs.h>
|
|
|
|
|
|
|
|
|
|
#ifndef irq_canonicalize
|
|
|
|
|
#define irq_canonicalize(i) (i)
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifndef NR_IRQS
|
|
|
|
|
#define NR_IRQS 128
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Use this value to indicate lack of interrupt
|
|
|
|
|
* capability
|
|
|
|
|
*/
|
|
|
|
|
#ifndef NO_IRQ
|
|
|
|
|
#define NO_IRQ ((unsigned int)(-1))
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
struct irqaction;
|
|
|
|
|
|
[PATCH] IRQ type flags
Some ARM platforms have the ability to program the interrupt controller to
detect various interrupt edges and/or levels. For some platforms, this is
critical to setup correctly, particularly those which the setting is dependent
on the device.
Currently, ARM drivers do (eg) the following:
err = request_irq(irq, ...);
set_irq_type(irq, IRQT_RISING);
However, if the interrupt has previously been programmed to be level sensitive
(for whatever reason) then this will cause an interrupt storm.
Hence, if we combine set_irq_type() with request_irq(), we can then safely set
the type prior to unmasking the interrupt. The unfortunate problem is that in
order to support this, these flags need to be visible outside of the ARM
architecture - drivers such as smc91x need these flags and they're
cross-architecture.
Finally, the SA_TRIGGER_* flag passed to request_irq() should reflect the
property that the device would like. The IRQ controller code should do its
best to select the most appropriate supported mode.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
19 years ago
|
|
|
/*
|
|
|
|
|
* Migration helpers
|
[PATCH] IRQ type flags
Some ARM platforms have the ability to program the interrupt controller to
detect various interrupt edges and/or levels. For some platforms, this is
critical to setup correctly, particularly those which the setting is dependent
on the device.
Currently, ARM drivers do (eg) the following:
err = request_irq(irq, ...);
set_irq_type(irq, IRQT_RISING);
However, if the interrupt has previously been programmed to be level sensitive
(for whatever reason) then this will cause an interrupt storm.
Hence, if we combine set_irq_type() with request_irq(), we can then safely set
the type prior to unmasking the interrupt. The unfortunate problem is that in
order to support this, these flags need to be visible outside of the ARM
architecture - drivers such as smc91x need these flags and they're
cross-architecture.
Finally, the SA_TRIGGER_* flag passed to request_irq() should reflect the
property that the device would like. The IRQ controller code should do its
best to select the most appropriate supported mode.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
19 years ago
|
|
|
*/
|
|
|
|
|
#define __IRQT_FALEDGE IRQ_TYPE_EDGE_FALLING
|
|
|
|
|
#define __IRQT_RISEDGE IRQ_TYPE_EDGE_RISING
|
|
|
|
|
#define __IRQT_LOWLVL IRQ_TYPE_LEVEL_LOW
|
|
|
|
|
#define __IRQT_HIGHLVL IRQ_TYPE_LEVEL_HIGH
|
|
|
|
|
|
|
|
|
|
#define IRQT_NOEDGE (0)
|
|
|
|
|
#define IRQT_RISING (__IRQT_RISEDGE)
|
|
|
|
|
#define IRQT_FALLING (__IRQT_FALEDGE)
|
|
|
|
|
#define IRQT_BOTHEDGE (__IRQT_RISEDGE|__IRQT_FALEDGE)
|
|
|
|
|
#define IRQT_LOW (__IRQT_LOWLVL)
|
|
|
|
|
#define IRQT_HIGH (__IRQT_HIGHLVL)
|
|
|
|
|
#define IRQT_PROBE IRQ_TYPE_PROBE
|
|
|
|
|
|
|
|
|
|
extern void migrate_irqs(void);
|
|
|
|
|
#endif
|
|
|
|
|
|
