Kconfig 2.2 KB

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