Kconfig 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147
  1. #
  2. # DMA engine configuration
  3. #
  4. menuconfig DMADEVICES
  5. bool "DMA Engine support"
  6. depends on HAS_DMA
  7. help
  8. DMA engines can do asynchronous data transfers without
  9. involving the host CPU. Currently, this framework can be
  10. used to offload memory copies in the network stack and
  11. RAID operations in the MD driver. This menu only presents
  12. DMA Device drivers supported by the configured arch, it may
  13. be empty in some cases.
  14. if DMADEVICES
  15. comment "DMA Devices"
  16. config ASYNC_TX_DISABLE_CHANNEL_SWITCH
  17. bool
  18. config INTEL_IOATDMA
  19. tristate "Intel I/OAT DMA support"
  20. depends on PCI && X86
  21. select DMA_ENGINE
  22. select DCA
  23. select ASYNC_TX_DISABLE_CHANNEL_SWITCH
  24. help
  25. Enable support for the Intel(R) I/OAT DMA engine present
  26. in recent Intel Xeon chipsets.
  27. Say Y here if you have such a chipset.
  28. If unsure, say N.
  29. config INTEL_IOP_ADMA
  30. tristate "Intel IOP ADMA support"
  31. depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
  32. select DMA_ENGINE
  33. help
  34. Enable support for the Intel(R) IOP Series RAID engines.
  35. config DW_DMAC
  36. tristate "Synopsys DesignWare AHB DMA support"
  37. depends on AVR32
  38. select DMA_ENGINE
  39. default y if CPU_AT32AP7000
  40. help
  41. Support the Synopsys DesignWare AHB DMA controller. This
  42. can be integrated in chips such as the Atmel AT32ap7000.
  43. config AT_HDMAC
  44. tristate "Atmel AHB DMA support"
  45. depends on ARCH_AT91SAM9RL
  46. select DMA_ENGINE
  47. help
  48. Support the Atmel AHB DMA controller. This can be integrated in
  49. chips such as the Atmel AT91SAM9RL.
  50. config FSL_DMA
  51. tristate "Freescale Elo and Elo Plus DMA support"
  52. depends on FSL_SOC
  53. select DMA_ENGINE
  54. ---help---
  55. Enable support for the Freescale Elo and Elo Plus DMA controllers.
  56. The Elo is the DMA controller on some 82xx and 83xx parts, and the
  57. Elo Plus is the DMA controller on 85xx and 86xx parts.
  58. config MV_XOR
  59. bool "Marvell XOR engine support"
  60. depends on PLAT_ORION
  61. select DMA_ENGINE
  62. ---help---
  63. Enable support for the Marvell XOR engine.
  64. config MX3_IPU
  65. bool "MX3x Image Processing Unit support"
  66. depends on ARCH_MX3
  67. select DMA_ENGINE
  68. default y
  69. help
  70. If you plan to use the Image Processing unit in the i.MX3x, say
  71. Y here. If unsure, select Y.
  72. config MX3_IPU_IRQS
  73. int "Number of dynamically mapped interrupts for IPU"
  74. depends on MX3_IPU
  75. range 2 137
  76. default 4
  77. help
  78. Out of 137 interrupt sources on i.MX31 IPU only very few are used.
  79. To avoid bloating the irq_desc[] array we allocate a sufficient
  80. number of IRQ slots and map them dynamically to specific sources.
  81. config TXX9_DMAC
  82. tristate "Toshiba TXx9 SoC DMA support"
  83. depends on MACH_TX49XX || MACH_TX39XX
  84. select DMA_ENGINE
  85. help
  86. Support the TXx9 SoC internal DMA controller. This can be
  87. integrated in chips such as the Toshiba TX4927/38/39.
  88. config SH_DMAE
  89. tristate "Renesas SuperH DMAC support"
  90. depends on SUPERH && SH_DMA
  91. depends on !SH_DMA_API
  92. select DMA_ENGINE
  93. help
  94. Enable support for the Renesas SuperH DMA controllers.
  95. config DMA_ENGINE
  96. bool
  97. comment "DMA Clients"
  98. depends on DMA_ENGINE
  99. config NET_DMA
  100. bool "Network: TCP receive copy offload"
  101. depends on DMA_ENGINE && NET
  102. default (INTEL_IOATDMA || FSL_DMA)
  103. help
  104. This enables the use of DMA engines in the network stack to
  105. offload receive copy-to-user operations, freeing CPU cycles.
  106. Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
  107. say N.
  108. config ASYNC_TX_DMA
  109. bool "Async_tx: Offload support for the async_tx api"
  110. depends on DMA_ENGINE
  111. help
  112. This allows the async_tx api to take advantage of offload engines for
  113. memcpy, memset, xor, and raid6 p+q operations. If your platform has
  114. a dma engine that can perform raid operations and you have enabled
  115. MD_RAID456 say Y.
  116. If unsure, say N.
  117. config DMATEST
  118. tristate "DMA Test client"
  119. depends on DMA_ENGINE
  120. help
  121. Simple DMA test client. Say N unless you're debugging a
  122. DMA Device driver.
  123. endif