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

 
 
 
 
 
  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# Support for generic irq migrating off cpu before the cpu is offline.
 34config GENERIC_IRQ_MIGRATION
 35	bool
 36
 37# Alpha specific irq affinity mechanism
 38config AUTO_IRQ_AFFINITY
 39       bool
 40
 41# Tasklet based software resend for pending interrupts on enable_irq()
 42config HARDIRQS_SW_RESEND
 43       bool
 44
 45# Preflow handler support for fasteoi (sparc64)
 46config IRQ_PREFLOW_FASTEOI
 47       bool
 48
 49# Edge style eoi based handler (cell)
 50config IRQ_EDGE_EOI_HANDLER
 51       bool
 52
 53# Generic configurable interrupt chip implementation
 54config GENERIC_IRQ_CHIP
 55       bool
 56       select IRQ_DOMAIN
 57
 58# Generic irq_domain hw <--> linux irq number translation
 59config IRQ_DOMAIN
 60	bool
 61
 62# Support for hierarchical irq domains
 63config IRQ_DOMAIN_HIERARCHY
 64	bool
 65	select IRQ_DOMAIN
 66
 67# Generic IRQ IPI support
 68config GENERIC_IRQ_IPI
 69	bool
 70
 71# Generic MSI interrupt support
 72config GENERIC_MSI_IRQ
 73	bool
 74
 75# Generic MSI hierarchical interrupt domain support
 76config GENERIC_MSI_IRQ_DOMAIN
 77	bool
 78	select IRQ_DOMAIN_HIERARCHY
 79	select GENERIC_MSI_IRQ
 80
 81config HANDLE_DOMAIN_IRQ
 82	bool
 83
 84config IRQ_DOMAIN_DEBUG
 85	bool "Expose hardware/virtual IRQ mapping via debugfs"
 86	depends on IRQ_DOMAIN && DEBUG_FS
 87	help
 88	  This option will show the mapping relationship between hardware irq
 89	  numbers and Linux irq numbers. The mapping is exposed via debugfs
 90	  in the file "irq_domain_mapping".
 91
 92	  If you don't know what this means you don't need it.
 93
 94# Support forced irq threading
 95config IRQ_FORCED_THREADING
 96       bool
 97
 98config SPARSE_IRQ
 99	bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
100	---help---
101
102	  Sparse irq numbering is useful for distro kernels that want
103	  to define a high CONFIG_NR_CPUS value but still want to have
104	  low kernel memory footprint on smaller machines.
105
106	  ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
107	    out the interrupt descriptors in a more NUMA-friendly way. )
108
109	  If you don't know what to do here, say N.
110
111endmenu