From: Vinod Koul <vinod.koul@intel.com>
To: Matt Porter <mporter@ti.com>
Cc: Chris Ball <cjb@laptop.org>, Dan Williams <djbw@fb.com>,
Sekhar Nori <nsekhar@ti.com>,
Grant Likely <grant.likely@secretlab.ca>,
Linux DaVinci Kernel List
<davinci-linux-open-source@linux.davincidsp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MMC List <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] dmaengine: add slave sg transfer limits api
Date: Thu, 21 Mar 2013 12:16:43 +0530 [thread overview]
Message-ID: <20130321064643.GG10326@intel.com> (raw)
In-Reply-To: <1362599767-11292-1-git-send-email-mporter@ti.com>
On Wed, Mar 06, 2013 at 02:56:04PM -0500, Matt Porter wrote:
> Changes since v3:
> - Change api name to dma_get_slave_sg_limits() to avoid
> confusion with h/w caps which are static.
>
> Changes since v2:
> - Change to a separate slave sg specific api. Drop the
> generic per-channel capabilities api that is not used.
>
> Changes since v1:
> - Use the existing dma_transaction_type enums instead of
> adding the mostly duplicated dmaengine_apis enums
>
> This series adds a new dmaengine api, dma_get_slave_sg_limits(), which
> may be used by a client driver to get slave SG transfer limits for a
> particular channel. At this time, these include the max number of
> segments and max length of a segment that a channel can handle for a
> SG transfer.
Looks fine, should be ready for merge once we fix the API.
Also I was under the impression that you will add another API to calculate the
limits, the stuff which you were doing in caps API earlier.
--
~Vinod
>
> Along with the API implementation, this series implements the backend
> device_slave_sg_limits() in the EDMA DMA Engine driver and converts the
> davinci_mmc driver to use dma_get_slave_sg_limits() to replace hardcoded
> limits.
>
> This is tested on the AM1808-EVM.
>
> Matt Porter (3):
> dmaengine: add dma_get_slave_sg_limits()
> dma: edma: add device_slave_sg_limits() support
> mmc: davinci: get SG segment limits with dma_get_slave_sg_limits()
>
> drivers/dma/edma.c | 17 +++++++++++++
> drivers/mmc/host/davinci_mmc.c | 37 ++++++++-------------------
> include/linux/dmaengine.h | 39 +++++++++++++++++++++++++++++
> include/linux/platform_data/mmc-davinci.h | 3 ---
> 4 files changed, 66 insertions(+), 30 deletions(-)
>
> --
> 1.7.9.5
>
prev parent reply other threads:[~2013-03-21 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 19:56 [PATCH v4 0/3] dmaengine: add slave sg transfer limits api Matt Porter
2013-03-06 19:56 ` [PATCH v4 1/3] dmaengine: add dma_get_slave_sg_limits() Matt Porter
2013-03-11 16:57 ` Lars-Peter Clausen
2013-03-21 6:43 ` Vinod Koul
2013-05-29 12:19 ` Lars-Peter Clausen
2013-03-06 19:56 ` [PATCH v4 2/3] dma: edma: add device_slave_sg_limits() support Matt Porter
2013-03-06 19:56 ` [PATCH v4 3/3] mmc: davinci: get SG segment limits with dma_get_slave_sg_limits() Matt Porter
2013-03-21 6:46 ` Vinod Koul [this message]
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=20130321064643.GG10326@intel.com \
--to=vinod.koul@intel.com \
--cc=cjb@laptop.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=djbw@fb.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mporter@ti.com \
--cc=nsekhar@ti.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).