From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>, vinod.koul@intel.com
Cc: dan.j.williams@intel.com, grant.likely@secretlab.ca,
linux-kernel@vger.kernel.org, olof@lixom.net,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V5 2/2] dma: tegra: add dmaengine based dma driver
Date: Wed, 06 Jun 2012 11:47:17 -0600 [thread overview]
Message-ID: <4FCF97A5.5040008@wwwdotorg.org> (raw)
In-Reply-To: <1338960327-31453-2-git-send-email-ldewangan@nvidia.com>
On 06/05/2012 11:25 PM, Laxman Dewangan wrote:
> Add dmaengine based NVIDIA's Tegra APB DMA driver.
> This driver support the slave mode of data transfer from
> peripheral to memory and vice versa.
> The driver supports for the cyclic and non-cyclic mode
> of data transfer.
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
Laxman, what are you plans for enabling this and replacing the existing
non-dmaengine APB DMA driver? We will need to convert:
* The fuse WAR stuff in arch/arm/mach-tegra
* The ASoC driver in sound/soc/tegra
This will require some thought and dependency management between the
various subsystems.
Vinod,
It may be best to apply this series along in a topic branch that you
merge into the dmaengine branch, and I can pull into Tegra if/when I
need. Or, if you ack it, I can take it all through the Tegra tree if you
want. That wouldn't allow patch 1 to be use by others though.
Thanks.
next prev parent reply other threads:[~2012-06-06 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 5:25 [PATCH V5 1/2] dma: dmaengine: add slave req id in slave_config Laxman Dewangan
2012-06-06 5:25 ` Laxman Dewangan
2012-06-06 5:25 ` [PATCH V5 2/2] dma: tegra: add dmaengine based dma driver Laxman Dewangan
2012-06-06 5:25 ` Laxman Dewangan
2012-06-06 17:47 ` Stephen Warren [this message]
[not found] ` <4FCF97A5.5040008-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-06-06 17:52 ` Laxman Dewangan
2012-06-06 17:52 ` Laxman Dewangan
[not found] ` <1338960327-31453-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-08 5:33 ` Vinod Koul
2012-06-08 5:33 ` Vinod Koul
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=4FCF97A5.5040008@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=dan.j.williams@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=vinod.koul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.