From: Laxman Dewangan <ldewangan@nvidia.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Stephen Warren <swarren@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V1] dmaengine: tegra: add dma driver
Date: Wed, 25 Apr 2012 15:12:33 +0530 [thread overview]
Message-ID: <4F97C709.2060807@nvidia.com> (raw)
In-Reply-To: <1335346425.31825.118.camel@vkoul-udesk3>
On Wednesday 25 April 2012 03:03 PM, Vinod Koul wrote:
> 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?
I am referring the Nvidia Tegra's APB dma driver. This will be
completely new driver based on dmaengine. We have old dma driver under
mach-tegra/dma.c which has tegra specific apis. Want to move this driver
to generic dmaengine based api.
Russell is working on Omap's dma driver.
These are completely independent driver.
next prev parent reply other threads:[~2012-04-25 9:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 9:08 [PATCH V1] dmaengine: tegra: add dma driver Laxman Dewangan
2012-04-20 11:14 ` Vinod Koul
2012-04-20 12:16 ` Laxman Dewangan
2012-04-20 13:45 ` Laxman Dewangan
2012-04-23 8:41 ` Vinod Koul
2012-04-23 12:17 ` Laxman Dewangan
2012-04-23 12:23 ` Vinod Koul
2012-04-23 13:06 ` Russell King - ARM Linux
2012-04-23 13:17 ` Laxman Dewangan
2012-04-25 9:01 ` Laxman Dewangan
2012-04-25 9:33 ` Vinod Koul
2012-04-25 9:42 ` Laxman Dewangan [this message]
2012-04-25 9:43 ` Vinod Koul
2012-04-25 9:58 ` Laxman Dewangan
2012-04-25 10:35 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F97C709.2060807@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.com \
--cc=vinod.koul@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox