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 simulated interrupts
 67config IRQ_SIM
 68	bool
 69	select IRQ_WORK
 70
 71# Support for hierarchical irq domains
 72config IRQ_DOMAIN_HIERARCHY
 73	bool
 74	select IRQ_DOMAIN
 75
 76# Support for hierarchical fasteoi+edge and fasteoi+level handlers
 77config IRQ_FASTEOI_HIERARCHY_HANDLERS
 78	bool
 79
 80# Generic IRQ IPI support
 81config GENERIC_IRQ_IPI
 82	bool
 83
 84# Generic MSI interrupt support
 85config GENERIC_MSI_IRQ
 86	bool
 87
 88# Generic MSI hierarchical interrupt domain support
 89config GENERIC_MSI_IRQ_DOMAIN
 90	bool
 91	select IRQ_DOMAIN_HIERARCHY
 92	select GENERIC_MSI_IRQ
 93
 94config HANDLE_DOMAIN_IRQ
 95	bool
 96
 97config IRQ_TIMINGS
 98	bool
 99
100config GENERIC_IRQ_MATRIX_ALLOCATOR
101	bool
102
103config GENERIC_IRQ_RESERVATION_MODE
104	bool
105
106# Support forced irq threading
107config IRQ_FORCED_THREADING
108       bool
109
110config SPARSE_IRQ
111	bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
112	---help---
113
114	  Sparse irq numbering is useful for distro kernels that want
115	  to define a high CONFIG_NR_CPUS value but still want to have
116	  low kernel memory footprint on smaller machines.
117
118	  ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
119	    out the interrupt descriptors in a more NUMA-friendly way. )
120
121	  If you don't know what to do here, say N.
122
123config GENERIC_IRQ_DEBUGFS
124	bool "Expose irq internals in debugfs"
125	depends on DEBUG_FS
126	default n
127	---help---
128
129	  Exposes internal state information through debugfs. Mostly for
130	  developers and debugging of hard to diagnose interrupt problems.
131
132	  If you don't know what to do here, say N.
133
134endmenu
135
136config GENERIC_IRQ_MULTI_HANDLER
137	depends on !MULTI_IRQ_HANDLER
138	bool
139	help
140	  Allow to specify the low level IRQ handler at run time.

 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# Enable the generic irq autoprobe mechanism
 9config GENERIC_IRQ_PROBE
10	bool
11
12# Use the generic /proc/interrupts implementation
13config GENERIC_IRQ_SHOW
14       bool
15
16# Print level/edge extra information
17config GENERIC_IRQ_SHOW_LEVEL
18       bool
19
 
 
 
 
 
 
 
 
 
20# Support for delayed migration from interrupt context
21config GENERIC_PENDING_IRQ
22	bool
23
 
 
 
 
24# Alpha specific irq affinity mechanism
25config AUTO_IRQ_AFFINITY
26       bool
27
28# Tasklet based software resend for pending interrupts on enable_irq()
29config HARDIRQS_SW_RESEND
30       bool
31
32# Preflow handler support for fasteoi (sparc64)
33config IRQ_PREFLOW_FASTEOI
34       bool
35
36# Edge style eoi based handler (cell)
37config IRQ_EDGE_EOI_HANDLER
38       bool
39
40# Generic configurable interrupt chip implementation
41config GENERIC_IRQ_CHIP
42       bool
43       select IRQ_DOMAIN
44
45# Generic irq_domain hw <--> linux irq number translation
46config IRQ_DOMAIN
47	bool
48
49config IRQ_DOMAIN_DEBUG
50	bool "Expose hardware/virtual IRQ mapping via debugfs"
51	depends on IRQ_DOMAIN && DEBUG_FS
52	help
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".
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
56
57	  If you don't know what this means you don't need it.
 
58
59# Support forced irq threading
60config IRQ_FORCED_THREADING
61       bool
62
63config SPARSE_IRQ
64	bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
65	---help---
66
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.
70
71	  ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
72	    out the interrupt descriptors in a more NUMA-friendly way. )
73
74	  If you don't know what to do here, say N.
75
 
 
 
 
 
 
 
 
 
 
 
76endmenu