xref: /openbmc/linux/kernel/irq/Kconfig (revision 4562236b) 
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# Supports effective affinity mask
25config GENERIC_IRQ_EFFECTIVE_AFF_MASK
26       bool
27
28# Facility to allocate a hardware interrupt. This is legacy support
29# and should not be used in new code. Use irq domains instead.
30config GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
31       bool
32
33# Support for delayed migration from interrupt context
34config GENERIC_PENDING_IRQ
35	bool
36
37# Support for generic irq migrating off cpu before the cpu is offline.
38config GENERIC_IRQ_MIGRATION
39	bool
40
41# Alpha specific irq affinity mechanism
42config AUTO_IRQ_AFFINITY
43       bool
44
45# Tasklet based software resend for pending interrupts on enable_irq()
46config HARDIRQS_SW_RESEND
47       bool
48
49# Preflow handler support for fasteoi (sparc64)
50config IRQ_PREFLOW_FASTEOI
51       bool
52
53# Edge style eoi based handler (cell)
54config IRQ_EDGE_EOI_HANDLER
55       bool
56
57# Generic configurable interrupt chip implementation
58config GENERIC_IRQ_CHIP
59       bool
60       select IRQ_DOMAIN
61
62# Generic irq_domain hw <--> linux irq number translation
63config IRQ_DOMAIN
64	bool
65
66# Support for hierarchical irq domains
67config IRQ_DOMAIN_HIERARCHY
68	bool
69	select IRQ_DOMAIN
70
71# Generic IRQ IPI support
72config GENERIC_IRQ_IPI
73	bool
74
75# Generic MSI interrupt support
76config GENERIC_MSI_IRQ
77	bool
78
79# Generic MSI hierarchical interrupt domain support
80config GENERIC_MSI_IRQ_DOMAIN
81	bool
82	select IRQ_DOMAIN_HIERARCHY
83	select GENERIC_MSI_IRQ
84
85config HANDLE_DOMAIN_IRQ
86	bool
87
88config IRQ_TIMINGS
89	bool
90
91config IRQ_DOMAIN_DEBUG
92	bool "Expose hardware/virtual IRQ mapping via debugfs"
93	depends on IRQ_DOMAIN && DEBUG_FS
94	help
95	  This option will show the mapping relationship between hardware irq
96	  numbers and Linux irq numbers. The mapping is exposed via debugfs
97	  in the file "irq_domain_mapping".
98
99	  If you don't know what this means you don't need it.
100
101# Support forced irq threading
102config IRQ_FORCED_THREADING
103       bool
104
105config SPARSE_IRQ
106	bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
107	---help---
108
109	  Sparse irq numbering is useful for distro kernels that want
110	  to define a high CONFIG_NR_CPUS value but still want to have
111	  low kernel memory footprint on smaller machines.
112
113	  ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
114	    out the interrupt descriptors in a more NUMA-friendly way. )
115
116	  If you don't know what to do here, say N.
117
118config GENERIC_IRQ_DEBUGFS
119	bool "Expose irq internals in debugfs"
120	depends on DEBUG_FS
121	default n
122	---help---
123
124	  Exposes internal state information through debugfs. Mostly for
125	  developers and debugging of hard to diagnose interrupt problems.
126
127	  If you don't know what to do here, say N.
128
129endmenu
130