[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C79549CB6F772498162A641D92D5328D9FE16@penmb01.corp.atmel.com>
Date: Tue, 18 Jan 2011 09:43:45 +0800
From: "Xu, Hong" <Hong.Xu@...el.com>
To: "Ryan Mallon" <ryan@...ewatersys.com>
Cc: <linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>, <jamie@...ieiles.com>,
<jacmet@...site.dk>, "Nicolas Ferre" <nicolas.ferre@...el.com>
Subject: RE: [PATCH] MTD: atmel_nand: Add DMA support to access Nandflash
Hi Ryan,
> -----Original Message-----
> From: Ryan Mallon [mailto:ryan@...ewatersys.com]
> Sent: Tuesday, January 18, 2011 6:42 AM
> To: Xu, Hong
> Cc: linux-mtd@...ts.infradead.org; linux-arm-kernel@...ts.infradead.org;
> linux-kernel@...r.kernel.org; jamie@...ieiles.com; jacmet@...site.dk;
> Ferre, Nicolas
> Subject: Re: [PATCH] MTD: atmel_nand: Add DMA support to access Nandflash
>
> root@...pper:~$ dmesg | grep -i dma
> [ 0.850000] atmel_nand atmel_nand: Failed to request DMA channel
> [ 0.860000] atmel_nand atmel_nand: No DMA support for NAND access.
> [ 1.530000] at_hdmac at_hdmac: Atmel AHB DMA Controller ( cpy slave ),
> 8 channels
>
>
> It looks like the registration for the DMA controller happens after the
> NAND driver probe and so the request is failing. I had a quick look, but
> I can't see anything that would change this in more recent kernels. Any
> ideas?
>
You got the point. A [Git Pull] has been sent, see
http://article.gmane.org/gmane.linux.kernel/1088240/match=dmaengine+update
In this patch, subsys_initcall will be used so DMA engine will be initialized before NAND driver.
Thanks.
BR,
Hong
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists