xref: /linux/drivers/dma/qcom/Kconfig (revision 7f8f209fd6e09a07fd1820144452caba419cf2b4)
1d9b31efcSSinan Kayaconfig QCOM_BAM_DMA
2d9b31efcSSinan Kaya	tristate "QCOM BAM DMA support"
3d9b31efcSSinan Kaya	depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM)
4d9b31efcSSinan Kaya	select DMA_ENGINE
5d9b31efcSSinan Kaya	select DMA_VIRTUAL_CHANNELS
6d9b31efcSSinan Kaya	---help---
7d9b31efcSSinan Kaya	  Enable support for the QCOM BAM DMA controller.  This controller
8d9b31efcSSinan Kaya	  provides DMA capabilities for a variety of on-chip devices.
9*7f8f209fSSinan Kaya
10*7f8f209fSSinan Kayaconfig QCOM_HIDMA_MGMT
11*7f8f209fSSinan Kaya	tristate "Qualcomm Technologies HIDMA Management support"
12*7f8f209fSSinan Kaya	select DMA_ENGINE
13*7f8f209fSSinan Kaya	help
14*7f8f209fSSinan Kaya	  Enable support for the Qualcomm Technologies HIDMA Management.
15*7f8f209fSSinan Kaya	  Each DMA device requires one management interface driver
16*7f8f209fSSinan Kaya	  for basic initialization before QCOM_HIDMA channel driver can
17*7f8f209fSSinan Kaya	  start managing the channels. In a virtualized environment,
18*7f8f209fSSinan Kaya	  the guest OS would run QCOM_HIDMA channel driver and the
19*7f8f209fSSinan Kaya	  host would run the QCOM_HIDMA_MGMT management driver.
20