On Thu, 2014-10-09 at 23:09 -0700, GIRISH HALADY wrote: > Please see inline comment: > > grep DMA .config ? > > # DMA engine configuration > menuconfig DMADEVICES No. .config is a file in the kernel source tree when you build the actual kernel. There you may see the status of the kernel parts, drivers and subsystems (enabled, disabled, module). My question was to check what exactly do you have there regarding to DMA. > bool "DMA Engine support" > depends on HAS_DMA > DMA engines can do asynchronous data transfers without > DMA Device drivers supported by the configured arch, it may > config DMADEVICES_DEBUG > bool "DMA Engine debugging" > depends on DMADEVICES != n > say N here. This enables DMA engine core and driver debugging. > config DMADEVICES_VDEBUG > bool "DMA Engine verbose debugging" > depends on DMADEVICES_DEBUG != n > the DMA engine core and drivers. > if DMADEVICES > comment "DMA Devices" > config INTEL_MID_DMAC > tristate "Intel MID DMA support for Peripheral DMA controllers" > select DMA_ENGINE > Enable support for the Intel(R) MID DMA engine present > select DMA_ENGINE > select DMA_VIRTUAL_CHANNELS > Platform has a PL08x DMAC device > which can provide DMA engine support > config INTEL_IOATDMA > tristate "Intel I/OAT DMA support" > select DMA_ENGINE > select DMA_ENGINE_RAID > Enable support for the Intel(R) I/OAT DMA engine present > config INTEL_IOP_ADMA > tristate "Intel IOP ADMA support" > select DMA_ENGINE > config AT_HDMAC > tristate "Atmel AHB DMA support" > select DMA_ENGINE > Support the Atmel AHB DMA controller. > config FSL_DMA > tristate "Freescale Elo series DMA support" > select DMA_ENGINE > Enable support for the Freescale Elo series DMA controllers. > The Elo is the DMA controller on some mpc82xx and mpc83xx parts, the > config MPC512X_DMA > tristate "Freescale MPC512x built-in DMA engine support" > select DMA_ENGINE > Enable support for the Freescale MPC512x built-in DMA engine. > > select DMA_ENGINE > select DMA_ENGINE_RAID > select DMA_ENGINE > config TXX9_DMAC > tristate "Toshiba TXx9 SoC DMA support" > select DMA_ENGINE > Support the TXx9 SoC internal DMA controller. This can be > config TEGRA20_APB_DMA > bool "NVIDIA Tegra20 APB DMA support" > select DMA_ENGINE > Support for the NVIDIA Tegra20 APB DMA controller driver. The > DMA controller is having multiple DMA channel which can be > This DMA controller transfers data from memory to peripheral fifo > config S3C24XX_DMAC > tristate "Samsung S3C24XX DMA support" > depends on ARCH_S3C24XX && !S3C24XX_DMA > select DMA_ENGINE > select DMA_VIRTUAL_CHANNELS > Support for the Samsung S3C24XX DMA controller driver. The > DMA controller is having multiple DMA channels which can be > The DMA controller can transfer data from memory to peripheral, > bool "ST-Ericsson COH901318 DMA support" > select DMA_ENGINE > Support for ST-Ericsson DMA40 controller > config AMCC_PPC440SPE_ADMA > tristate "AMCC PPC440SPe ADMA support" > select DMA_ENGINE > select DMA_ENGINE_RAID > config TIMB_DMA > tristate "Timberdale FPGA DMA support" > select DMA_ENGINE > Enable support for the Timberdale FPGA DMA engine. > config SIRF_DMA > tristate "CSR SiRFprimaII/SiRFmarco DMA support" > select DMA_ENGINE > Enable support for the CSR SiRFprimaII DMA engine. > config TI_EDMA > bool "TI EDMA support" > select DMA_ENGINE > select DMA_VIRTUAL_CHANNELS > select TI_PRIV_EDMA > Enable support for the TI EDMA controller. This DMA > config PL330_DMA > tristate "DMA API Driver for PL330" > select DMA_ENGINE > Select if your platform has one or more PL330 DMACs. > config PCH_DMA > tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA" > select DMA_ENGINE > Enable support for Intel EG20T PCH DMA engine. > config IMX_SDMA > tristate "i.MX SDMA support" > select DMA_ENGINE > Support the i.MX SDMA engine. This engine is integrated into > config IMX_DMA > config PL330_DMA > tristate "DMA API Driver for PL330" > select DMA_ENGINE > Select if your platform has one or more PL330 DMACs. > config PCH_DMA > tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA" > select DMA_ENGINE Enable support for Intel EG20T PCH DMA engine. > config IMX_SDMA > tristate "i.MX SDMA support" > select DMA_ENGINE > Support the i.MX SDMA engine. This engine is integrated into > config IMX_DMA > tristate "i.MX DMA support" > select DMA_ENGINE > Support the i.MX DMA engine. This engine is integrated into > config MXS_DMA > bool "MXS DMA support" > select DMA_ENGINE > Support the MXS DMA engine. This engine including APBH-DMA > and APBX-DMA is integrated into Freescale i.MX23/28 chips. > > > However, the DMAtest just does NOT just work. Please help getting > this resolved. > > > Best Regards > Girish > > On Thu, Oct 9, 2014 at 10:41 PM, GIRISH HALADY <girish.halady@xxxxxxxxx> wrote: > > Hi Andy, > > Apologize, i still couldn't get the dmatest to work either > > compiled with the kernel or compiled as a kernel module. Would greatly > > help if you could help list the steps specifically for running this > > test on Opensource Linux with Microzed ZC7010. > > > > Thanks and Best Regards > > Girish > > > > On Thu, Oct 9, 2014 at 1:12 AM, GIRISH HALADY <girish.halady@xxxxxxxxx> wrote: > >> Hi Andy, > >> Please ignore my earlier e-mail. In an attempt to compile > >> the DYNAMIC_DEBUG, I forgot to compile the dmatest under the > >> dma_drivers. Now with the test included, it still gives the same > >> error. > >> > >>> zynq> dmatest.channel=dma0chan0 dmatest.timeout=2000 dmatest.iteration > >>> s=1 dmatest.run=1 > >>> -/bin/ash: dmatest.channel=dma0chan0: not found > >> > >> What I suspect is that it may not have a Shell instance. Could you > >> please help clarify what Shell is needed by the test to run? Do we > >> need to install a shell separately in the kernel image? > >> > >> Thanks & Best Regards > >> Girish Halady > >> > >> On Mon, Oct 6, 2014 at 4:20 AM, Andy Shevchenko > >> <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > >>> On Sun, 2014-10-05 at 23:56 -0700, GIRISH HALADY wrote: > >>>> Hi Andiry, > >>>> Thanks for the post on www.kernel.org: > >>>> https://www.kernel.org/doc/Documentation/dmatest.txt > >>>> > >>>> > >>> First of all, I dared to answer this mail publicly. Please, keep the > >>> mailing list address in the Cc list (dmaengine@xxxxxxxxxxxxxxx) for now > >>> and for any future mail regarding to DMA engine subsystem related > >>> issues. > >>>> > >>>> I was trying to run this test on my target (Microzed Zynq7010 board). > >>>> I could get the dmatest compiled within the kernel. However, when I > >>>> try running the command I get some strange error. Thought I check > >>>> with you if I am missing something. > >>> > >>>> The objective that I setforth was to be able to run the dmatest from > >>>> DDR to a RAM instance in the Programmable Logic which is mapped to the > >>>> processing system (PS7) that runs dual-ARM A9 and an embedded linux > >>>> kernel on it. > >>> > >>>> zynq> modprobe dmatest channel=dma0chan0 timeout=2000 iterations=1 run > >>>> =1 > >>>> modprobe: chdir(3.14.0-xilinx-dirty): No such file or directory > >>>> > >>>> Kernel command : ERROR > >>> > >>>> zynq> dmatest.channel=dma0chan0 dmatest.timeout=2000 dmatest.iteration > >>>> s=1 dmatest.run=1 > >>>> -/bin/ash: dmatest.channel=dma0chan0: not found > >>> > >>>> Please help me understand how I go about fixing this. > >>>> > >>> Have you tried to get the list of available dma channels first as > >>> suggested by the documentation? > >>> > >>> "Hint: available channel list could be extracted by running the > >>> following command: > >>> % ls -1 /sys/class/dma/ > >>> " > >>> > >>> > >>> -- > >>> Andy Shevchenko <andriy.shevchenko@xxxxxxxxx> > >>> Intel Finland Oy > >>> -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxx> Intel Finland Oy -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
