From: Laxman Dewangan <ldewangan@nvidia.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: rmk <rmk@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>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>
Subject: Re: [PATCH V1] dmaengine: tegra: add dma driver
Date: Mon, 23 Apr 2012 17:47:03 +0530 [thread overview]
Message-ID: <4F95483F.5020005@nvidia.com> (raw)
In-Reply-To: <1335170491.31825.104.camel@vkoul-udesk3>
Hi Russell,
On Monday 23 April 2012 02:11 PM, Vinod Koul wrote:
> On Fri, 2012-04-20 at 17:46 +0530, Laxman Dewangan wrote:
>> Thanks Vinod for quick review.
> Since I was on vacation, I hadn't noticed Russell has already sent the
> patches for omap dma support.
> http://permalink.gmane.org/gmane.linux.ports.arm.omap/75034
>
> It would be nice if both the efforts are coordinated.
>
> Btw I like the virtual channel support introduced by Russell
>
Can you please point me the virtual channel related change? I am not
able to locate this like search for function vchan_* ().
My driver is also on same line but not used vchan_* and also having
support for cyclic transfer.
next prev parent reply other threads:[~2012-04-23 12:18 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 [this message]
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
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=4F95483F.5020005@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=rmk@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