Version:  2.0.40 2.2.26 2.4.37 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 3.16 3.17

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

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