Re: [PATCH v1 5/5] ARM: mxs: add mxs dma dt support

2012-03-27 Thread Huang Shijie 

Hi Aisheng:

The non-dt way also does not have interrupt resource for dma device.
It seems the channel interrupt resource is handled in each client device.
I'm not familiar with gpmi-nand, but I guess you may need to handle
it in gpmi driver, just like mxs-mmc driver.


ok, got it.

thanks
Huang Shijie


___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: [PATCH v1 5/5] ARM: mxs: add mxs dma dt support

2012-03-27 Thread Huang Shijie 

Hi,

+   dma-apbh@80004000 {
+   compatible = "fsl,mxs-dma-apbh";
+   reg =<0x80004000 2000>;
+   };
+

Why you do not add the `interrupt` for the it?
the gpmi-nand needs to parse the interrupt out.

BR
Huang Shijie


___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: [PATCH v1 5/5] ARM: mxs: add mxs dma dt support

2012-03-14 Thread Dong Aisheng 
On Wed, Mar 14, 2012 at 03:58:23PM +0800, Huang Shijie-B32955 wrote:
> Hi,
> > +   dma-apbh@80004000 {
> > +   compatible = "fsl,mxs-dma-apbh";
> > +   reg =<0x80004000 2000>;
> > +   };
> > +
> Why you do not add the `interrupt` for the it?
> the gpmi-nand needs to parse the interrupt out.
> 
The non-dt way also does not have interrupt resource for dma device.
It seems the channel interrupt resource is handled in each client device.
I'm not familiar with gpmi-nand, but I guess you may need to handle
it in gpmi driver, just like mxs-mmc driver.

Regards
Dong Aisheng

___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss