Kconfig 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config QCOM_ADM
  3. tristate "Qualcomm ADM support"
  4. depends on (ARCH_QCOM || COMPILE_TEST) && !PHYS_ADDR_T_64BIT
  5. select DMA_ENGINE
  6. select DMA_VIRTUAL_CHANNELS
  7. help
  8. Enable support for the Qualcomm Application Data Mover (ADM) DMA
  9. controller, as present on MSM8x60, APQ8064, and IPQ8064 devices.
  10. This controller provides DMA capabilities for both general purpose
  11. and on-chip peripheral devices.
  12. config QCOM_BAM_DMA
  13. tristate "QCOM BAM DMA support"
  14. depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM)
  15. select DMA_ENGINE
  16. select DMA_VIRTUAL_CHANNELS
  17. help
  18. Enable support for the QCOM BAM DMA controller. This controller
  19. provides DMA capabilities for a variety of on-chip devices.
  20. config QCOM_GPI_DMA
  21. tristate "Qualcomm Technologies GPI DMA support"
  22. depends on ARCH_QCOM
  23. select DMA_ENGINE
  24. select DMA_VIRTUAL_CHANNELS
  25. help
  26. Enable support for the QCOM GPI DMA controller. This controller
  27. provides DMA capabilities for a variety of peripheral buses such
  28. as I2C, UART, and SPI. By using GPI dmaengine driver, bus drivers
  29. can use a standardize interface that is protocol independent to
  30. transfer data between DDR and peripheral.
  31. config MSM_GPI_DMA
  32. tristate "Qualcomm Technologies Inc GPI DMA support"
  33. depends on ARCH_QCOM
  34. select DMA_ENGINE
  35. select DMA_VIRTUAL_CHANNELS
  36. help
  37. Enable support for the QCOM GPI DMA controller. This controller
  38. provides DMA capabilities for a variety of peripheral buses such
  39. as I2C, UART, and SPI. By using GPI dmaengine driver, bus drivers
  40. can use a standardize interface that is protocol independent to
  41. transfer data between DDR and peripheral.
  42. config MSM_GPI_DMA_DEBUG
  43. bool "Qualcomm Technologies Inc GPI debug support"
  44. depends on MSM_GPI_DMA
  45. help
  46. Enable detailed logging for QCOM GPI driver. Extra logging will be
  47. helpful when debugging critical issues. By using GPI dmaengine driver,
  48. bus drivers can use a standardize interface that is protocol independent
  49. to transfer data between DDR and peripheral.
  50. config QCOM_HIDMA_MGMT
  51. tristate "Qualcomm Technologies HIDMA Management support"
  52. depends on HAS_IOMEM
  53. select DMA_ENGINE
  54. help
  55. Enable support for the Qualcomm Technologies HIDMA Management.
  56. Each DMA device requires one management interface driver
  57. for basic initialization before QCOM_HIDMA channel driver can
  58. start managing the channels. In a virtualized environment,
  59. the guest OS would run QCOM_HIDMA channel driver and the
  60. host would run the QCOM_HIDMA_MGMT management driver.
  61. config QCOM_HIDMA
  62. tristate "Qualcomm Technologies HIDMA Channel support"
  63. select DMA_ENGINE
  64. help
  65. Enable support for the Qualcomm Technologies HIDMA controller.
  66. The HIDMA controller supports optimized buffer copies
  67. (user to kernel, kernel to kernel, etc.). It only supports
  68. memcpy interface. The core is not intended for general
  69. purpose slave DMA.