2 # Options selectable by the architecture code
4 # Make sparse irq Kconfig switch below available
5 config MAY_HAVE_SPARSE_IRQ
8 # Enable the generic irq autoprobe mechanism
9 config GENERIC_IRQ_PROBE
12 # Use the generic /proc/interrupts implementation
13 config GENERIC_IRQ_SHOW
16 # Print level/edge extra information
17 config GENERIC_IRQ_SHOW_LEVEL
20 # Support for delayed migration from interrupt context
21 config GENERIC_PENDING_IRQ
24 # Alpha specific irq affinity mechanism
25 config AUTO_IRQ_AFFINITY
28 # Tasklet based software resend for pending interrupts on enable_irq()
29 config HARDIRQS_SW_RESEND
32 # Preflow handler support for fasteoi (sparc64)
33 config IRQ_PREFLOW_FASTEOI
36 # Edge style eoi based handler (cell)
37 config IRQ_EDGE_EOI_HANDLER
40 # Generic configurable interrupt chip implementation
41 config GENERIC_IRQ_CHIP
45 # Generic irq_domain hw <--> linux irq number translation
49 config IRQ_DOMAIN_DEBUG
50 bool "Expose hardware/virtual IRQ mapping via debugfs"
51 depends on IRQ_DOMAIN && DEBUG_FS
53 This option will show the mapping relationship between hardware irq
54 numbers and Linux irq numbers. The mapping is exposed via debugfs
55 in the file "irq_domain_mapping".
57 If you don't know what this means you don't need it.
59 # Support forced irq threading
60 config IRQ_FORCED_THREADING
64 bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
67 Sparse irq numbering is useful for distro kernels that want
68 to define a high CONFIG_NR_CPUS value but still want to have
69 low kernel memory footprint on smaller machines.
71 ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
72 out the interrupt descriptors in a more NUMA-friendly way. )
74 If you don't know what to do here, say N.