2 # Options selectable by the architecture code
4 # Make sparse irq Kconfig switch below available
5 config MAY_HAVE_SPARSE_IRQ
8 # Legacy support, required for itanic
9 config GENERIC_IRQ_LEGACY
12 # Enable the generic irq autoprobe mechanism
13 config GENERIC_IRQ_PROBE
16 # Use the generic /proc/interrupts implementation
17 config GENERIC_IRQ_SHOW
20 # Print level/edge extra information
21 config GENERIC_IRQ_SHOW_LEVEL
24 # Supports effective affinity mask
25 config GENERIC_IRQ_EFFECTIVE_AFF_MASK
28 # Facility to allocate a hardware interrupt. This is legacy support
29 # and should not be used in new code. Use irq domains instead.
30 config GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
33 # Support for delayed migration from interrupt context
34 config GENERIC_PENDING_IRQ
37 # Support for generic irq migrating off cpu before the cpu is offline.
38 config GENERIC_IRQ_MIGRATION
41 # Alpha specific irq affinity mechanism
42 config AUTO_IRQ_AFFINITY
45 # Tasklet based software resend for pending interrupts on enable_irq()
46 config HARDIRQS_SW_RESEND
49 # Preflow handler support for fasteoi (sparc64)
50 config IRQ_PREFLOW_FASTEOI
53 # Edge style eoi based handler (cell)
54 config IRQ_EDGE_EOI_HANDLER
57 # Generic configurable interrupt chip implementation
58 config GENERIC_IRQ_CHIP
62 # Generic irq_domain hw <--> linux irq number translation
66 # Support for simulated interrupts
71 # Support for hierarchical irq domains
72 config IRQ_DOMAIN_HIERARCHY
76 # Support for hierarchical fasteoi+edge and fasteoi+level handlers
77 config IRQ_FASTEOI_HIERARCHY_HANDLERS
80 # Generic IRQ IPI support
81 config GENERIC_IRQ_IPI
84 # Generic MSI interrupt support
85 config GENERIC_MSI_IRQ
88 # Generic MSI hierarchical interrupt domain support
89 config GENERIC_MSI_IRQ_DOMAIN
91 select IRQ_DOMAIN_HIERARCHY
92 select GENERIC_MSI_IRQ
94 config HANDLE_DOMAIN_IRQ
100 config IRQ_DOMAIN_DEBUG
101 bool "Expose hardware/virtual IRQ mapping via debugfs"
102 depends on IRQ_DOMAIN && DEBUG_FS
104 This option will show the mapping relationship between hardware irq
105 numbers and Linux irq numbers. The mapping is exposed via debugfs
106 in the file "irq_domain_mapping".
108 If you don't know what this means you don't need it.
110 # Support forced irq threading
111 config IRQ_FORCED_THREADING
115 bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
118 Sparse irq numbering is useful for distro kernels that want
119 to define a high CONFIG_NR_CPUS value but still want to have
120 low kernel memory footprint on smaller machines.
122 ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
123 out the interrupt descriptors in a more NUMA-friendly way. )
125 If you don't know what to do here, say N.
127 config GENERIC_IRQ_DEBUGFS
128 bool "Expose irq internals in debugfs"
133 Exposes internal state information through debugfs. Mostly for
134 developers and debugging of hard to diagnose interrupt problems.
136 If you don't know what to do here, say N.