Loading...
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 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
59# Support forced irq threading
60config IRQ_FORCED_THREADING
61 bool
62
63config SPARSE_IRQ
64 bool "Support sparse irq numbering"
65 depends on HAVE_SPARSE_IRQ
66 ---help---
67
68 Sparse irq numbering is useful for distro kernels that want
69 to define a high CONFIG_NR_CPUS value but still want to have
70 low kernel memory footprint on smaller machines.
71
72 ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
73 out the interrupt descriptors in a more NUMA-friendly way. )
74
75 If you don't know what to do here, say N.
76
77endmenu
78endif
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