- 19 May, 2017 1 commit
-
-
Arnd Bergmann authored
The new driver requires both mailbox and raid support for compile testing: drivers/dma/built-in.o: In function `sba_remove': edma.c:(.text+0x4414): undefined reference to `mbox_free_channel' drivers/dma/built-in.o: In function `sba_issue_pending': edma.c:(.text+0x46cc): undefined reference to `mbox_send_message' drivers/dma/built-in.o: In function `sba_probe': edma.c:(.text+0x4e60): undefined reference to `mbox_request_channel' edma.c:(.text+0x5038): undefined reference to `mbox_free_channel' drivers/dma/built-in.o: In function `sba_tx_status': edma.c:(.text+0x5210): undefined reference to `mbox_client_peek_data' drivers/dma/built-in.o: In function `sba_prep_dma_pq_req': edma.c:(.text+0x5784): undefined reference to `raid6_gflog' edma.c:(.text+0x5798): undefined reference to `raid6_gflog' This rearranges the Kconfig dependencies accordingly. Fixes: 743e1c8f ("dmaengine: Add Broadcom SBA RAID driver") Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 16 May, 2017 1 commit
-
-
Anup Patel authored
The Broadcom stream buffer accelerator (SBA) provides offloading capabilities for RAID operations. This SBA offload engine is accessible via Broadcom SoC specific ring manager. This patch adds Broadcom SBA RAID driver which provides one DMA device with RAID capabilities using one or more Broadcom SoC specific ring manager channels. The SBA RAID driver in its current shape implements memcpy, xor, and pq operations. Signed-off-by:
Anup Patel <anup.patel@broadcom.com> Reviewed-by:
Ray Jui <ray.jui@broadcom.com> Acked-by:
Dan Williams <dan.j.williams@intel.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 01 May, 2017 1 commit
-
-
Stefan Roese authored
To enable usage of multiple SG buffers via the sg_buffers= module parameter, lets select DMA_ENGINE_RAID via Kconfig when DMATEST is configured. Otherwise the dmatest will "BUG" when more than 1 buffer (total of 2 for src + dst) is configured via sg_buffers. Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Kedareswara rao Appana <appanad@xilinx.com> Cc: Vinod Koul <vinod.koul@intel.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 07 Mar, 2017 1 commit
-
-
Alexandre Bailon authored
The DA8xx has a CPPI 4.1 DMA controller. This is add the glue layer required to make it work on DA8xx. Signed-off-by:
Alexandre Bailon <abailon@baylibre.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 05 Feb, 2017 1 commit
-
-
Icenowy Zheng authored
As 64-bit Allwinner H5 SoC has the same DMA engine with H3, the DMA driver should be allowed to be built for ARM64, in order to make it work on H5. Signed-off-by:
Icenowy Zheng <icenowy@aosc.xyz> Acked-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by:
Chen-Yu Tsai <wens@csie.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 03 Jan, 2017 1 commit
-
-
M'boumba Cedric Madianga authored
As STM32 DMA driver is only used as buit-in driver, it couldn't be used as module. Signed-off-by:
M'boumba Cedric Madianga <cedric.madianga@gmail.com> Reviewed-by:
Ludovic BARRE <ludovic.barre@st.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 02 Jan, 2017 1 commit
-
-
Shawn Guo authored
ZTE ZX dma driver is not ZX296702 specific. It works for not only ZX296702 but also other ZTE ZX family platforms like ZX296718. Let's rename the file to reflect that. Signed-off-by:
Shawn Guo <shawn.guo@linaro.org> Reviewed-by:
Jun Nie <jun.nie@linaro.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 17 Nov, 2016 1 commit
-
-
Vinod Koul authored
This reverts commit 6d066389 "(dmaengine: st_fdma: Revert: Update st_fdma to 'depends on REMOTEPROC')" as the commit it reverted was fine. Reported-by:
Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 14 Nov, 2016 2 commits
-
-
Vinod Koul authored
This reverts commit 184e1396 ("dmaengine: st_fdma: Update st_fdma to 'depends on REMOTEPROC'") due to objection from Bjorn. Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Paul Gortmaker authored
This driver currently uses modular infrastructure but is controlled by a bool Kconfig. There is a general consensus from the DMA reviewers and maintainers that "if it can be modular, it should be modular" in order to keep the bzImage size under control for multi platform kernels. Build tested only. Also needed some new pm_clk symbols exported before this commit is applied to tree in order to avoid modpost errors like: ERROR: "pm_clk_add_clk" [drivers/dma/tegra210-adma.ko] undefined! ERROR: "pm_clk_create" [drivers/dma/tegra210-adma.ko] undefined! ERROR: "pm_clk_destroy" [drivers/dma/tegra210-adma.ko] undefined! ERROR: "pm_clk_suspend" [drivers/dma/tegra210-adma.ko] undefined! ERROR: "pm_clk_resume" [drivers/dma/tegra210-adma.ko] undefined! These were added as exports in the v4.8-rc1 merge window. Cc: Laxman Dewangan <ldewangan@nvidia.com> Cc: Jon Hunter <jonathanh@nvidia.com> Acked-by:
Jon Hunter <jonathanh@nvidia.com> Cc: Dan Williams <dan.j.williams@intel.com> Cc: Vinod Koul <vinod.koul@intel.com> Cc: Stephen Warren <swarren@wwwdotorg.org> Cc: Thierry Reding <thierry.reding@gmail.com> Cc: Alexandre Courbot <gnurou@gmail.com> Cc: dmaengine@vger.kernel.org Cc: linux-tegra@vger.kernel.org Signed-off-by:
Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 03 Nov, 2016 1 commit
-
-
Peter Griffin authored
During randconfig builds you can get the following warning "warning: (ST_FDMA) selects ST_SLIM_REMOTEPROC which has unmet direct dependencies (REMOTEPROC)" randconfig builds should always build without any warnings so update fdma to depend on REMOTEPROC so this can not happen. Signed-off-by:
Peter Griffin <peter.griffin@linaro.org> Reported-by:
Arnd Bergmann <arnd@arndb.de> Tested-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 18 Oct, 2016 2 commits
-
-
Jérémy Lefaure authored
There are some compilation errors when CONFIG_MMP_TDMA is enabled and CONFIG_GENERIC_ALLOCATOR is disabled: drivers/built-in.o: In function `mmp_tdma_prep_dma_cyclic': mmp_tdma.c:(.text+0x7890e): undefined reference to `gen_pool_dma_alloc' drivers/built-in.o: In function `mmp_tdma_free_chan_resources': mmp_tdma.c:(.text+0x78aca): undefined reference to `gen_pool_free' drivers/built-in.o: In function `mmp_tdma_probe': mmp_tdma.c:(.text+0x78ea8): undefined reference to `of_gen_pool_get' This commit fix this problem by selecting GENERIC_ALLOCATOR when CONFIG_MMP_TDMA is enabled. Signed-off-by:
Jérémy Lefaure <jeremy.lefaure@lse.epita.fr> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Peter Griffin authored
This patch adds support for the Flexible Direct Memory Access (FDMA) core driver. The FDMA is a slim core CPU with a dedicated firmware. It is a general purpose DMA controller capable of supporting 16 independent DMA channels. Data moves maybe from memory to memory or between memory and paced latency critical real time targets and it is found on al STi based chipsets. Signed-off-by:
Ludovic Barre <ludovic.barre@st.com> Signed-off-by:
Peter Griffin <peter.griffin@linaro.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 28 Sep, 2016 3 commits
-
-
Peter Ujfalusi authored
To get more coverage, enable COMPILE_TEST for this driver. When compile testing eDMA or omap-dma, select also the ti-dma-crossbar so it is also covered by the compile testing. Signed-off-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Peter Ujfalusi authored
To get more coverage, enable COMPILE_TEST for this driver. Signed-off-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Peter Ujfalusi authored
To get more coverage, enable COMPILE_TEST for this driver. Signed-off-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 27 Sep, 2016 1 commit
-
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Suggested-by:
Jon Hunter <jonathanh@nvidia.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 26 Sep, 2016 13 commits
-
-
Vinod Koul authored
We have unmet direct dependencies as DMA_SUN4I selects DMA_OF so remove the selection warning: (DMA_SUN4I && MOXART_DMA && STM32_DMA) selects DMA_OF which has unmet direct dependencies (DMADEVICES && OF) Suggested-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
We have unmet direct dependencies as DMA_SUN4I selects DMA_OF so remove the selection warning: (DMA_SUN4I && MOXART_DMA && STM32_DMA) selects DMA_OF which has unmet direct dependencies (DMADEVICES && OF) Suggested-by:
Arnd Bergmann <arnd@arndb.de> Acked-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Reviewed-by:
Krzysztof Kozlowski <krzk@kernel.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. While at it, to fix build on other archs, select MMP_SRAM only for ARCH_MMP and also fix the platform header Suggested-by:
Arnd Bergmann <arnd@arndb.de> Acked-by:
Zhangfei Gao <zhangfei.gao@linaro.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Acked-by:
Zhangfei Gao <zhangfei.gao@linaro.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Acked-by:
Russell King <rmk+kernel@armlinux.org.uk> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Acked-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Vinod Koul authored
To get more coverage, enable COMPILE_TEST for this driver. Acked-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 31 Aug, 2016 1 commit
-
-
John Stultz authored
This allows the k3dma driver to be selected on HiKey via the ARCH_HISI dependency. Cc: Zhangfei Gao <zhangfei.gao@linaro.org> Cc: Jingoo Han <jg1.han@samsung.com> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com> Cc: Maxime Ripard <maxime.ripard@free-electrons.com> Cc: Vinod Koul <vinod.koul@intel.com> Cc: Dan Williams <dan.j.williams@intel.com> Cc: Mark Brown <broonie@kernel.org> Cc: Andy Green <andy@warmcat.com> Acked-by:
Zhangfei Gao <zhangfei.gao@linaro.org> Signed-off-by:
John Stultz <john.stultz@linaro.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 12 Jul, 2016 1 commit
-
-
Thomas Petazzoni authored
The new mv_xor_v2 driver supports the XOR engines found in the 64-bits ARM from Marvell of the Armada 7K and Armada 8K family. This XOR engine is a completely new hardware block, entirely different from the one used on previous Marvell Armada platforms, which use the existing mv_xor driver. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 08 Jul, 2016 2 commits
-
-
Kedareswara rao Appana authored
Added the driver for zynqmp dma engine used in Zynq UltraScale+ MPSoC. This dma controller supports memory to memory and I/O to I/O buffer transfers. Signed-off-by:
Kedareswara rao Appana <appanad@xilinx.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
Kedareswara rao Appana authored
In the existing vdma driver support for AXI DMA and CDMA got added so the driver is no longer VDMA specific. This patch renames the driver and DT binding doc to xilinx_dma and updates the Kconfig description for all the DMAS. Signed-off-by:
Kedareswara rao Appana <appanad@xilinx.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 13 May, 2016 1 commit
-
-
Jon Hunter authored
Add support for the Tegra210 Audio DMA controller that is used for transferring data between system memory and the Audio sub-system. The driver only supports cyclic transfers because this is being solely used for audio. This driver is based upon the work by Dara Ramesh <dramesh@nvidia.com>. Signed-off-by:
Jon Hunter <jonathanh@nvidia.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 03 May, 2016 1 commit
-
-
Gregory CLEMENT authored
Armada 3700 SoC uses the mv_xor driver but don't select anymore the PLAT_ORION symbol. This commit extends the dependency of the mv_xor driver to the more modern SoCs only compatible with ARCH_MVEBU, which allows using it with the Armada 3700 SoC. In the same time it also add the COMPILE_TEST dependency allowing a wider test coverage. Signed-off-by:
Gregory CLEMENT <gregory.clement@free-electrons.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 06 Apr, 2016 1 commit
-
-
Kedareswara rao Appana authored
This VDMA is a soft ip, which can be programmed to support 32 bit addressing or greater than 32 bit addressing. When the VDMA ip is configured for 32 bit address space the buffer address is specified by a single register (0x5C for MM2S and 0xAC for S2MM channel). When the VDMA core is configured for an address space greater than 32 then each buffer address is specified by a combination of two registers. The first register specifies the LSB 32 bits of address, while the next register specifies the MSB 32 bits of address. For example, 5Ch will specify the LSB 32 bits while 60h will specify the MSB 32 bits of the first start address. So we need to program two registers at a time. This patch adds the 64 bit addressing support to the vdma driver. Signed-off-by:
Anurag Kumar Vulisha <anuragku@xilinx.com> Signed-off-by:
Kedareswara rao Appana <appanad@xilinx.com> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 11 Mar, 2016 1 commit
-
-
Sinan Kaya authored
Creating a QCOM directory for all QCOM DMA source files. Signed-off-by:
Sinan Kaya <okaya@codeaurora.org> Reviewed-by:
Andy Gross <agross@codeaurora.org> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 22 Feb, 2016 1 commit
-
-
Lothar Waßmann authored
The mxs-dma unit is also available on i.MX6UL. Make it possible to select it in Kconfig. Signed-off-by:
Lothar Waßmann <LW@KARO-electronics.de> Signed-off-by:
Vinod Koul <vinod.koul@intel.com>
-
- 21 Nov, 2015 1 commit
-
-
Arnd Bergmann authored
As we are now passing the filter data as pointers to the drivers, we can take the final step and also pass the filter function the same way. I'm keeping this change separate, as there it's less obvious that this is a net win. Upsides of this are: - The ASoC drivers are completely independent from the DMA engine implementation, which simplifies the Kconfig logic and in theory allows the same sound drivers to be built in a kernel that supports different kinds of dmaengine drivers. - Consistency with other subsystems and drivers On the other hand, we have a few downsides: - The s3c24xx-dma driver now needs to be built-in for the ac97 platform device to be instantiated on s3c2440. - samsung_dmaengine_pcm_config cannot be marked 'const' any more because the filter function pointer needs to be set at runtime. This is safe as long we don't have multiple different DMA engines in thet same system at runtime, but is nonetheless ugly. Signed-off-by:...
-