From: Vinod Koul <vinod.koul@intel.com>
To: Joel Fernandes <joelf@ti.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>, Dan Williams <djbw@fb.com>,
Tony Lindgren <tony@atomide.com>, "Nori, Sekhar" <nsekhar@ti.com>,
Arnd Bergmann <arnd@arndb.de>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"Vutla, Lokesh" <lokeshvutla@ti.com>,
"Krishnamoorthy, Balaji T" <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: Thu, 25 Jul 2013 12:53:51 +0530 [thread overview]
Message-ID: <20130725072351.GJ18642@intel.com> (raw)
In-Reply-To: <51F02CBA.5060704@ti.com>
On Wed, Jul 24, 2013 at 02:36:26PM -0500, Joel Fernandes wrote:
> > Also another point worth considering is the approach Russell suggested, I havent
> > gotten a chance to dig deeper but if I understood it correctly then programming
> > the device_dma_parameters should be the right thing to do. Again I need to look
> > deeper and esp wrt edma
>
> OK. I have some patches sitting in my tree too that I'm working on. With
> that I don't need to know about maximum number of allowed segments and
> can send along any number of segment. I will rework them and post them.
> fwiw, I will also implement caps API incase like Lars did populating the
> other fields though these will not be unused.
>
> For segment size, at this time I don't know any driver that uses it
> other than davinci-pcm. For this reason the calculations can be done as
> Lars suggested (for minimum of maximum). Do you know in advance if
> you're going to amend to drop segment size if we go with what Russell
> suggested, or are you going to leave the seg-size in the caps API anyway.
I am just back and havent really done my work on this. Let me check and as I
said if my understanding is right I would be inclined to remove these fields...
~Vinod
--
next prev parent reply other threads:[~2013-07-25 7:23 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
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 [this message]
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=20130725072351.GJ18642@intel.com \
--to=vinod.koul@intel.com \
--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=lars@metafoo.de \
--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 \
/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).