From: Lars-Peter Clausen <lars@metafoo.de>
To: Joel Fernandes <joelf@ti.com>
Cc: Vinod Koul <vinod.koul@intel.com>, Dan Williams <djbw@fb.com>,
Tony Lindgren <tony@atomide.com>, Sekhar Nori <nsekhar@ti.com>,
Arnd Bergmann <arnd@arndb.de>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Rajendra Nayak <rnayak@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
Balaji TK <balajitk@ti.com>, Matt Porter <matt@ohporter.com>,
Rob Herring <rob.herring@calxeda.com>,
Jason Kridner <jkridner@beagleboard.org>,
Koen Kooi <koen@beagleboard.org>,
Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MMC List <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] dma: edma: add device_slave_caps() support
Date: Wed, 24 Jul 2013 10:03:30 +0200 [thread overview]
Message-ID: <51EF8A52.90902@metafoo.de> (raw)
In-Reply-To: <1374597804-3961-1-git-send-email-joelf@ti.com>
On 07/23/2013 06:43 PM, Joel Fernandes wrote:
> Implement device_slave_caps(). EDMA has a limited number of slots.
> Slave drivers such as omap_hsmmc will query the driver to make
> sure they don't pass in more than these many scatter segments.
>
> Signed-off-by: Joel Fernandes <joelf@ti.com>
> ---
> Vinod, or Dan- If this patch looks ok, can you please merge in for
> -rc cycle? This patch is required to fix MMC support on AM33xx. This
> patch is blocking 3 other patches which fix various MMC things. Thanks!
>
> Notes:
> (1) this approach is temporary and only for -rc cycle to fix MMC on
> AM335x. It will be replace by the RFC series in future kernels:
> http://www.spinics.net/lists/arm-kernel/msg260094.html
>
> (2) Patch depends Vinod's patch at:
> http://permalink.gmane.org/gmane.linux.kernel/1525112
>
> drivers/dma/edma.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c
> index 7222cbe..81d5429 100644
> --- a/drivers/dma/edma.c
> +++ b/drivers/dma/edma.c
> @@ -517,6 +517,14 @@ static void edma_issue_pending(struct dma_chan *chan)
> spin_unlock_irqrestore(&echan->vchan.lock, flags);
> }
>
> +static inline int edma_slave_caps(struct dma_chan *chan,
> + struct dma_slave_caps *caps)
> +{
> + caps->max_sg_nr = MAX_NR_SG;
Hm, what about the other fields?
- Lars
next prev parent reply other threads:[~2013-07-24 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 16:43 [PATCH] dma: edma: add device_slave_caps() support Joel Fernandes
2013-07-24 8:03 ` Lars-Peter Clausen [this message]
2013-07-24 8:11 ` Joel Fernandes
2013-07-24 8:24 ` Lars-Peter Clausen
2013-07-24 8:28 ` Fernandes, Joel
2013-07-24 8:40 ` Lars-Peter Clausen
2013-07-24 18:55 ` Joel Fernandes
2013-07-24 18:33 ` Vinod Koul
2013-07-24 19:36 ` Joel Fernandes
2013-07-25 7:23 ` Vinod Koul
2013-07-29 9:45 ` Vinod Koul
2013-07-30 4:39 ` Joel Fernandes
2013-07-24 19:15 ` Lars-Peter Clausen
2013-07-25 3:21 ` Fernandes, Joel
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=51EF8A52.90902@metafoo.de \
--to=lars@metafoo.de \
--cc=arnd@arndb.de \
--cc=balajitk@ti.com \
--cc=djbw@fb.com \
--cc=jkridner@beagleboard.org \
--cc=joelf@ti.com \
--cc=koen@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=matt@ohporter.com \
--cc=nsekhar@ti.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
--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).