1# SPDX-License-Identifier: GPL-2.0-only
  2menu "IRQ subsystem"
  3# Options selectable by the architecture code
  4
  5# Make sparse irq Kconfig switch below available
  6config MAY_HAVE_SPARSE_IRQ
  7       bool
  8
  9# Legacy support, required for itanic
 10config GENERIC_IRQ_LEGACY
 11       bool
 12
 13# Enable the generic irq autoprobe mechanism
 14config GENERIC_IRQ_PROBE
 15	bool
 16
 17# Use the generic /proc/interrupts implementation
 18config GENERIC_IRQ_SHOW
 19       bool
 20
 21# Print level/edge extra information
 22config GENERIC_IRQ_SHOW_LEVEL
 23       bool
 24
 25# Supports effective affinity mask
 26config GENERIC_IRQ_EFFECTIVE_AFF_MASK
 27       bool
 28
 29# Facility to allocate a hardware interrupt. This is legacy support
 30# and should not be used in new code. Use irq domains instead.
 31config GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
 32       bool
 33
 34# Support for delayed migration from interrupt context
 35config GENERIC_PENDING_IRQ
 36	bool
 37
 38# Support for generic irq migrating off cpu before the cpu is offline.
 39config GENERIC_IRQ_MIGRATION
 40	bool
 41
 42# Alpha specific irq affinity mechanism
 43config AUTO_IRQ_AFFINITY
 44       bool
 45
 46# Tasklet based software resend for pending interrupts on enable_irq()
 47config HARDIRQS_SW_RESEND
 48       bool
 49
 50# Preflow handler support for fasteoi (sparc64)
 51config IRQ_PREFLOW_FASTEOI
 52       bool
 53
 54# Edge style eoi based handler (cell)
 55config IRQ_EDGE_EOI_HANDLER
 56       bool
 57
 58# Generic configurable interrupt chip implementation
 59config GENERIC_IRQ_CHIP
 60       bool
 61       select IRQ_DOMAIN
 62
 63# Generic irq_domain hw <--> linux irq number translation
 64config IRQ_DOMAIN
 65	bool
 66
 67# Support for simulated interrupts
 68config IRQ_SIM
 69	bool
 70	select IRQ_WORK
 71
 72# Support for hierarchical irq domains
 73config IRQ_DOMAIN_HIERARCHY
 74	bool
 75	select IRQ_DOMAIN
 76
 77# Support for hierarchical fasteoi+edge and fasteoi+level handlers
 78config IRQ_FASTEOI_HIERARCHY_HANDLERS
 79	bool
 80
 81# Generic IRQ IPI support
 82config GENERIC_IRQ_IPI
 83	bool
 84
 85# Generic MSI interrupt support
 86config GENERIC_MSI_IRQ
 87	bool
 88
 89# Generic MSI hierarchical interrupt domain support
 90config GENERIC_MSI_IRQ_DOMAIN
 91	bool
 92	select IRQ_DOMAIN_HIERARCHY
 93	select GENERIC_MSI_IRQ
 94
 95config IRQ_MSI_IOMMU
 96	bool
 97
 98config HANDLE_DOMAIN_IRQ
 99	bool
100
101config IRQ_TIMINGS
102	bool
103
104config GENERIC_IRQ_MATRIX_ALLOCATOR
105	bool
 
 
106
107config GENERIC_IRQ_RESERVATION_MODE
108	bool
109
110# Support forced irq threading
111config IRQ_FORCED_THREADING
112       bool
113
114config SPARSE_IRQ
115	bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
116	---help---
117
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.
121
122	  ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
123	    out the interrupt descriptors in a more NUMA-friendly way. )
124
125	  If you don't know what to do here, say N.
126
127config GENERIC_IRQ_DEBUGFS
128	bool "Expose irq internals in debugfs"
129	depends on DEBUG_FS
130	default n
131	---help---
132
133	  Exposes internal state information through debugfs. Mostly for
134	  developers and debugging of hard to diagnose interrupt problems.
135
136	  If you don't know what to do here, say N.
137
138endmenu
139
140config GENERIC_IRQ_MULTI_HANDLER
141	bool
142	help
143	  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# 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