Hi Andy,
Please see my inlined comments on observation:
Okay, what about grep -H . /sys/class/dma/*/in_use ?
zynq> grep -H . /sys/class/dma/dma0chan*/in_use
/sys/class/dma/dma0chan0/in_use:0
/sys/class/dma/dma0chan1/in_use:0
/sys/class/dma/dma0chan2/in_use:0
/sys/class/dma/dma0chan3/in_use:0
/sys/class/dma/dma0chan4/in_use:0
/sys/class/dma/dma0chan5/in_use:0
/sys/class/dma/dma0chan6/in_use:0
/sys/class/dma/dma0chan7/in_use:0
Moreover, try to compile kernel with DYNAMIC_DEBUG=y and boot with
dmaengine.dyndbg appended to your kernel command line.
Did build the linux Kernel with CONFIG_DYNAMIC_DEBUG=y in the config
file and booted the kernel with dmaengine.dyndbg in the "bootargs"
Not sure what to expect from this? Please help clarify
> zynq> modprobe dmatest channel=dma0chan0 timeout=2000 iterations=1 run
> 1
> modprobe: chdir(3.14.0-xilinx-dirty): No such file or directory
grep DMA .config ?
zynq> grep DMA .config
grep: .config: No such file or directory
zynq> modprobe dmatest channel=dma0chan0 timeout=2000 iterations=1 run
1
modprobe: chdir(3.14.0-xilinx-dirty): No such file or directory
zynq> modprobe dmatest channel=dma0chan0 timeout=2000 iterations=1 run 1
modprobe: chdir(3.14.0-xilinx-dirty): No such file or directory
zynq> dmatest.channel=dma0chan0 dmatest.timeout=2000 dmatest.iteration
s=1 dmatest.run=1
-/bin/ash: dmatest.channel=dma0chan0: not found
I didn't get what you are trying to do with above.
This is the kernel option that you mentioned on the post. I was not
sure if the DMATEST was built as a kernel module or inside the kernel
image. HEnce tried both, but to no effect, unfotunately!
> Please suggest what needs to be changed to get this test to work.
>
So, currently I didn't see the problem with dmatest module, but rather
with your kernel and/or environment configuration.
Please help understand. Request some debug steps as I come from a
hardware background and am working on linux internals for the first
time. Please suggest if you would be avaiable on-line sometime to chat
on this.
Best Regards
Girish
On Wed, Oct 8, 2014 at 1:23 AM, Andy Shevchenko
<andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
> On Wed, 2014-10-08 at 00:22 -0700, GIRISH HALADY wrote:
>> Hi Andy,
>> Thanks for the reply. Apologize for the delay in getting back.
>
> Please, reply in line next time (no top postings).
>
>> I did try the step that you mentioned:
>>
>>
>> zynq> ls -1 /sys/class/dma/
>> dma0chan0
>> dma0chan1
>> dma0chan2
>> dma0chan3
>> dma0chan4
>> dma0chan5
>> dma0chan6
>> dma0chan7
>>
>>
>> Looks like all the 8 channels of PL330 are supported.
>
> Okay, what about grep -H . /sys/class/dma/*/in_use ?
>
> Moreover, try to compile kernel with DYNAMIC_DEBUG=y and boot with
> dmaengine.dyndbg appended to your kernel command line.
>
>
>> But as I said earlier, neither the kernel module method, nor the
>> built-in command method seems to work.
>>
>>
>> zynq> modprobe dmatest channel=dma0chan0 timeout=2000 iterations=1 run
>> 1
>> modprobe: chdir(3.14.0-xilinx-dirty): No such file or directory
>
> grep DMA .config ?
>
>> zynq> dmatest.channel=dma0chan0 dmatest.timeout=2000
>> dmatest.iterations=1 dmates
>> t.run=1
>> -/bin/ash: dmatest.channel=dma0chan0: not found
>
> I didn't get what you are trying to do with above.
>
>> Please suggest what needs to be changed to get this test to work.
>>
> So, currently I didn't see the problem with dmatest module, but rather
> with your kernel and/or environment configuration.
>>
>> > 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.
>
>
>
> --
> 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
