[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1335346425.31825.118.camel@vkoul-udesk3>
Date: Wed, 25 Apr 2012 15:03:45 +0530
From: Vinod Koul <vinod.koul@...ux.intel.com>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
Stephen Warren <swarren@...dia.com>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH V1] dmaengine: tegra: add dma driver
On Wed, 2012-04-25 at 14:31 +0530, Laxman Dewangan wrote:
>
> I had a communication with Russell on another change thread and
> understand that some more work need to be done in virt_chan to support
> cyclic one.
>
> I want to have the cyclic dma support in my driver so I want to go on
> following steps:
> 1. I will post the patch for tegra dma which will not use the virt_dma
> so that my driver will be independent of Russel's change.
which driver? A new driver for cyclic support only or on top of
Russell's changes?
> 2. Once the tegra dma is part of tree, I can move all my dma client to
> use the dmaengine based driver and remove old style dma.
> 3. Till that time Russell's will have already virt_dma support for
> cyclic one and so I will change tegra_dma.c to use virt_dma.
>
>
> Let me know your opinion so that I can plan my patch/change
> accordingly.
--
~Vinod
--
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