From: Daniel Mack <zonque@gmail.com>
To: Matt Porter <mporter@ti.com>
Cc: vinod.koul@intel.com, cjb@laptop.org, grant.likely@secretlab.ca,
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 v3 0/3] DaVinci DMA engine conversion
Date: Mon, 27 Aug 2012 17:33:19 +0200 [thread overview]
Message-ID: <503B933F.2030803@gmail.com> (raw)
In-Reply-To: <1345684176-21472-1-git-send-email-mporter@ti.com>
Hi Matt,
On 23.08.2012 03:09, Matt Porter wrote:
> This series begins the conversion of the DaVinci private EDMA API
> implementation to a DMA engine driver and converts two of the three
> in-kernel users of the private EDMA API to DMA engine.
>
> The approach taken is similar to the recent OMAP DMA Engine
> conversion. The EDMA DMA Engine driver is a wrapper around the existing
> private EDMA implementation and registers the platform device within
> the driver. This allows the conversion series to stand alone with just
> the drivers and no changes to platform code. It also allows peripheral
> drivers to continue to use the private EDMA implementation until they
> are converted.
>
> The EDMA DMA Engine driver supports slave transfers only at this time. It
> is planned to add cyclic transfers in support of audio peripherals.
>
> There are three users of the private EDMA API in the kernel now:
> davinci_mmc, spi-davinci, and davinci-mcasp. This series provides DMA
> Engine conversions for the davinci_mmc and spi-davinci drivers which
> use the supported slave transfers.
>
> This series has been tested on an AM18x EVM and Hawkboard with
> driver performance comparable to that of the private EDMA API
> implementations. Both MMC0 and MMC1 are tested which handles the
> DA850/OMAP-L138/AM18x specific case where MMC1 uses DMA channels on
> a second EDMA channel controller. All other platforms have a simpler
> design with just a single EDMA channel controller.
>
> For those wanting to easily test this series, I've pushed a branch for
> each version to my github tree at https://github.com/ohporter/linux. The
> current branch is edma-dmaengine-v3.
>
> After this series, the current plan is to complete the mcasp driver
> conversion which includes adding cyclic dma support. This will then
> enable the removal and refactoring of the private EDMA API functionality
> into the EDMA DMA Engine driver. Since EDMA is also used on the AM33xx
> family of parts in mach-omap2/, the plan is to enable this driver on
> that platform as well.
Once you have a patch for the McASP driver conversion, I can happily
test this on a AM33xx board, together with Gururaja's latest McASP
refactoring series. Let me know how I can help you here.
Thanks,
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] DaVinci DMA engine conversion
Date: Mon, 27 Aug 2012 17:33:19 +0200 [thread overview]
Message-ID: <503B933F.2030803@gmail.com> (raw)
In-Reply-To: <1345684176-21472-1-git-send-email-mporter@ti.com>
Hi Matt,
On 23.08.2012 03:09, Matt Porter wrote:
> This series begins the conversion of the DaVinci private EDMA API
> implementation to a DMA engine driver and converts two of the three
> in-kernel users of the private EDMA API to DMA engine.
>
> The approach taken is similar to the recent OMAP DMA Engine
> conversion. The EDMA DMA Engine driver is a wrapper around the existing
> private EDMA implementation and registers the platform device within
> the driver. This allows the conversion series to stand alone with just
> the drivers and no changes to platform code. It also allows peripheral
> drivers to continue to use the private EDMA implementation until they
> are converted.
>
> The EDMA DMA Engine driver supports slave transfers only at this time. It
> is planned to add cyclic transfers in support of audio peripherals.
>
> There are three users of the private EDMA API in the kernel now:
> davinci_mmc, spi-davinci, and davinci-mcasp. This series provides DMA
> Engine conversions for the davinci_mmc and spi-davinci drivers which
> use the supported slave transfers.
>
> This series has been tested on an AM18x EVM and Hawkboard with
> driver performance comparable to that of the private EDMA API
> implementations. Both MMC0 and MMC1 are tested which handles the
> DA850/OMAP-L138/AM18x specific case where MMC1 uses DMA channels on
> a second EDMA channel controller. All other platforms have a simpler
> design with just a single EDMA channel controller.
>
> For those wanting to easily test this series, I've pushed a branch for
> each version to my github tree at https://github.com/ohporter/linux. The
> current branch is edma-dmaengine-v3.
>
> After this series, the current plan is to complete the mcasp driver
> conversion which includes adding cyclic dma support. This will then
> enable the removal and refactoring of the private EDMA API functionality
> into the EDMA DMA Engine driver. Since EDMA is also used on the AM33xx
> family of parts in mach-omap2/, the plan is to enable this driver on
> that platform as well.
Once you have a patch for the McASP driver conversion, I can happily
test this on a AM33xx board, together with Gururaja's latest McASP
refactoring series. Let me know how I can help you here.
Thanks,
Daniel
next prev parent reply other threads:[~2012-08-27 15:33 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 1:09 [PATCH v3 0/3] DaVinci DMA engine conversion Matt Porter
2012-08-23 1:09 ` Matt Porter
2012-08-23 1:09 ` Matt Porter
[not found] ` <1345684176-21472-1-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2012-08-23 1:09 ` [PATCH v3 1/3] dmaengine: add TI EDMA DMA engine driver Matt Porter
2012-08-23 1:09 ` Matt Porter
2012-08-23 1:09 ` Matt Porter
2012-08-23 1:09 ` [PATCH v3 2/3] mmc: davinci_mmc: convert to DMA engine API Matt Porter
2012-08-23 1:09 ` Matt Porter
2012-08-23 1:09 ` Matt Porter
2012-08-23 1:09 ` [PATCH v3 3/3] spi: spi-davinci: " Matt Porter
2012-08-23 1:09 ` Matt Porter
2012-08-23 1:09 ` Matt Porter
[not found] ` <1345684176-21472-4-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2012-08-30 14:16 ` Sekhar Nori
2012-08-30 14:16 ` Sekhar Nori
2012-08-30 14:16 ` Sekhar Nori
2012-08-30 14:16 ` Sekhar Nori
2012-08-30 14:43 ` Matt Porter
2012-08-30 14:43 ` Matt Porter
2012-08-31 0:55 ` Vinod Koul
2012-08-31 0:55 ` Vinod Koul
2012-08-31 16:02 ` Sekhar Nori
2012-08-31 16:02 ` Sekhar Nori
2012-08-31 16:02 ` Sekhar Nori
2012-08-31 16:02 ` Sekhar Nori
2012-08-31 16:31 ` Vinod Koul
2012-08-31 16:31 ` Vinod Koul
2012-08-31 16:31 ` Sekhar Nori
2012-08-31 16:31 ` Sekhar Nori
2012-08-31 16:31 ` Sekhar Nori
2012-08-31 16:31 ` Sekhar Nori
2012-08-31 17:02 ` Vinod Koul
2012-08-31 17:02 ` Vinod Koul
2012-09-01 1:02 ` Vinod Koul
2012-09-01 1:02 ` Vinod Koul
2012-09-01 13:14 ` Matt Porter
2012-09-01 13:14 ` Matt Porter
2012-09-01 13:14 ` Matt Porter
2012-08-23 6:01 ` [PATCH v3 0/3] DaVinci DMA engine conversion Tom Rini
2012-08-23 6:01 ` Tom Rini
2012-08-27 15:33 ` Daniel Mack [this message]
2012-08-27 15:33 ` Daniel Mack
2012-09-06 13:25 ` Daniel Mack
2012-09-06 13:25 ` Daniel Mack
2012-09-10 20:20 ` Matt Porter
2012-09-10 20:20 ` 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=503B933F.2030803@gmail.com \
--to=zonque@gmail.com \
--cc=cjb@laptop.org \
--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=mporter@ti.com \
--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 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.