From: Vinod Koul <vinod.koul@linux.intel.com>
To: Matt Porter <mporter@ti.com>
Cc: cjb@laptop.org, grant.likely@secretlab.ca,
Linux DaVinci Kernel List
<davinci-linux-open-source@linux.davincidsp.com>,
Sekhar Nori <nsekhar@ti.com>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux SPI Devel List <spi-devel-general@lists.sourceforge.net>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 3/3] spi: spi-davinci: convert to DMA engine API
Date: Thu, 23 Aug 2012 09:29:40 +0530 [thread overview]
Message-ID: <1345694380.1895.87.camel@vkoul-udesk3> (raw)
In-Reply-To: <20120822160417.GA27758@beef>
On Wed, 2012-08-22 at 12:04 -0400, Matt Porter wrote:
> for querying of these types of limitations. Right now, the
> mmc driver implicitly knows that EDMA needs this restriction
> but it's something that should be queried before calling
> prep_slave().
that's something we need to add; exporting channel capabilities. We only
tell that it slave or memcpy today, but we need to tell clients what are
channel supported parameter ranges.
--
~Vinod
prev parent reply other threads:[~2012-08-23 3:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 18:43 [PATCH v2 0/3] DaVinci DMA engine conversion Matt Porter
2012-08-21 18:43 ` [PATCH v2 1/3] dmaengine: add TI EDMA DMA engine driver Matt Porter
2012-08-22 3:39 ` Vinod Koul
2012-08-22 16:21 ` Matt Porter
2012-08-22 12:37 ` Hebbar, Gururaja
2012-08-22 17:10 ` Matt Porter
2012-08-21 18:43 ` [PATCH v2 2/3] mmc: davinci_mmc: convert to DMA engine API Matt Porter
2012-08-22 18:53 ` Koen Kooi
2012-09-17 7:52 ` Chris Ball
2012-08-21 18:43 ` [PATCH v2 3/3] spi: spi-davinci: " Matt Porter
2012-08-22 3:45 ` Vinod Koul
2012-08-22 16:04 ` Matt Porter
2012-08-23 3:59 ` 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=1345694380.1895.87.camel@vkoul-udesk3 \
--to=vinod.koul@linux.intel.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 \
/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).