1menu "IRQ subsystem" 2# Options selectable by the architecture code 3 4# Make sparse irq Kconfig switch below available 5config MAY_HAVE_SPARSE_IRQ 6 bool 7 8# Legacy support, required for itanic 9config GENERIC_IRQ_LEGACY 10 bool 11 12# Enable the generic irq autoprobe mechanism 13config GENERIC_IRQ_PROBE 14 bool 15 16# Use the generic /proc/interrupts implementation 17config GENERIC_IRQ_SHOW 18 bool 19 20# Print level/edge extra information 21config GENERIC_IRQ_SHOW_LEVEL 22 bool 23 24# Facility to allocate a hardware interrupt. This is legacy support 25# and should not be used in new code. Use irq domains instead. 26config GENERIC_IRQ_LEGACY_ALLOC_HWIRQ 27 bool 28 29# Support for delayed migration from interrupt context 30config GENERIC_PENDING_IRQ 31 bool 32 33# Alpha specific irq affinity mechanism 34config AUTO_IRQ_AFFINITY 35 bool 36 37# Tasklet based software resend for pending interrupts on enable_irq() 38config HARDIRQS_SW_RESEND 39 bool 40 41# Preflow handler support for fasteoi (sparc64) 42config IRQ_PREFLOW_FASTEOI 43 bool 44 45# Edge style eoi based handler (cell) 46config IRQ_EDGE_EOI_HANDLER 47 bool 48 49# Generic configurable interrupt chip implementation 50config GENERIC_IRQ_CHIP 51 bool 52 select IRQ_DOMAIN 53 54# Generic irq_domain hw <--> linux irq number translation 55config IRQ_DOMAIN 56 bool 57 58config HANDLE_DOMAIN_IRQ 59 bool 60 61config IRQ_DOMAIN_DEBUG 62 bool "Expose hardware/virtual IRQ mapping via debugfs" 63 depends on IRQ_DOMAIN && DEBUG_FS 64 help 65 This option will show the mapping relationship between hardware irq 66 numbers and Linux irq numbers. The mapping is exposed via debugfs 67 in the file "irq_domain_mapping". 68 69 If you don't know what this means you don't need it. 70 71# Support forced irq threading 72config IRQ_FORCED_THREADING 73 bool 74 75config SPARSE_IRQ 76 bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ 77 ---help--- 78 79 Sparse irq numbering is useful for distro kernels that want 80 to define a high CONFIG_NR_CPUS value but still want to have 81 low kernel memory footprint on smaller machines. 82 83 ( Sparse irqs can also be beneficial on NUMA boxes, as they spread 84 out the interrupt descriptors in a more NUMA-friendly way. ) 85 86 If you don't know what to do here, say N. 87 88endmenu 89