On Wed, Apr 6, 2011 at 2:40 PM, Chuck Ketcham wrote:
> Three of the channels were not used because they were already publicly
> allocated. One channel was
> not used because it didn't have DMA_MEMCPY capability.
That's strange, because all four DMA channels are identical.
> 2. If dmaengine is
t;&mpic>;
> interrupts = <23 2>;
> };
> };
>
>
Your DTS file looks fine. It is what I would expect to see. The channels
are not allocated by anything here.
Turning on CONFIG_DMADEVICES_DEBUG may give
interrupt-parent = <&mpic>;
interrupts = <23 2>;
};
};
--- On Wed, 4/6/11, Ira W. Snyder wrote:
> From: Ira W. Snyder
> Subject: Re: Using dmaengine on Freescale P2020 RDB
> To: "Chuck K
On Wed, Apr 06, 2011 at 12:40:58PM -0700, Chuck Ketcham wrote:
> All,
>
> I have a Freescale P2020 Reference Design Board. I am investigating the
> possibility of using the dmaengine capability in the 2.6.32.13 kernel to
> transfer data from memory out onto the PCIe bus. As a first step, I tho
All,
I have a Freescale P2020 Reference Design Board. I am investigating the
possibility of using the dmaengine capability in the 2.6.32.13 kernel to
transfer data from memory out onto the PCIe bus. As a first step, I thought I
would try the DMA test client (dmatest.ko) to make sure the dmaen
