From: Matt Porter <mporter@ti.com>
To: vinod.koul@intel.com, dan.j.williams@intel.com, cjb@laptop.org,
grant.likely@secretlab.ca
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Linux SPI Devel List <spi-devel-general@lists.sourceforge.net>,
Linux DaVinci Kernel List
<davinci-linux-open-source@linux.davincidsp.com>,
Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH 1/3] dmaengine: add TI EDMA DMA engine driver
Date: Tue, 21 Aug 2012 14:20:04 -0400 [thread overview]
Message-ID: <20120821182004.GA32420@beef> (raw)
In-Reply-To: <1345153471-22757-2-git-send-email-mporter@ti.com>
On Thu, Aug 16, 2012 at 05:44:29PM -0400, Matt Porter wrote:
> Add a DMA engine driver for the TI EDMA controller. This driver
> is implemented as a wrapper around the existing DaVinci private
> DMA implementation. This approach allows for incremental conversion
> of each peripheral driver to the DMA engine API. The EDMA driver
> supports slave transfers but does not yet support cyclic transfers.
I got my hands on a AM18x WL12xx module so I could test MMC1 and this
exposed some bugs in the driver's handling of the second EDMA controller
case. DA850/OMAP-L138/AM1x have this second EDMA controller. I've
addressed this in v2 which will be posted shortly.
I'm expecting to receive a DM646x EVM RSN so I can cover testing that
part as well.
-Matt
next prev parent reply other threads:[~2012-08-21 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 21:44 [PATCH 0/3] DaVinci DMA engine conversion Matt Porter
[not found] ` <1345153471-22757-1-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2012-08-16 21:44 ` [PATCH 1/3] dmaengine: add TI EDMA DMA engine driver Matt Porter
2012-08-16 22:29 ` Russell King - ARM Linux
2012-08-20 14:17 ` Matt Porter
2012-08-21 18:20 ` Matt Porter [this message]
2012-08-16 21:44 ` [PATCH 2/3] mmc: davinci_mmc: convert to DMA engine API Matt Porter
2012-08-16 21:44 ` [PATCH 3/3] spi: spi-davinci: " Matt Porter
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=20120821182004.GA32420@beef \
--to=mporter@ti.com \
--cc=cjb@laptop.org \
--cc=dan.j.williams@intel.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=spi-devel-general@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).