Version:  2.0.40 2.2.26 2.4.37 2.6.39 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15

Linux/kernel/irq/Kconfig

  1 menu "IRQ subsystem"
  2 # Options selectable by the architecture code
  3 
  4 # Make sparse irq Kconfig switch below available
  5 config MAY_HAVE_SPARSE_IRQ
  6        bool
  7 
  8 # Enable the generic irq autoprobe mechanism
  9 config GENERIC_IRQ_PROBE
 10         bool
 11 
 12 # Use the generic /proc/interrupts implementation
 13 config GENERIC_IRQ_SHOW
 14        bool
 15 
 16 # Print level/edge extra information
 17 config GENERIC_IRQ_SHOW_LEVEL
 18        bool
 19 
 20 # Support for delayed migration from interrupt context
 21 config GENERIC_PENDING_IRQ
 22         bool
 23 
 24 # Alpha specific irq affinity mechanism
 25 config AUTO_IRQ_AFFINITY
 26        bool
 27 
 28 # Tasklet based software resend for pending interrupts on enable_irq()
 29 config HARDIRQS_SW_RESEND
 30        bool
 31 
 32 # Preflow handler support for fasteoi (sparc64)
 33 config IRQ_PREFLOW_FASTEOI
 34        bool
 35 
 36 # Edge style eoi based handler (cell)
 37 config IRQ_EDGE_EOI_HANDLER
 38        bool
 39 
 40 # Generic configurable interrupt chip implementation
 41 config GENERIC_IRQ_CHIP
 42        bool
 43        select IRQ_DOMAIN
 44 
 45 # Generic irq_domain hw <--> linux irq number translation
 46 config IRQ_DOMAIN
 47         bool
 48 
 49 config 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
 60 config IRQ_FORCED_THREADING
 61        bool
 62 
 63 config 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 
 76 endmenu

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us