From: Felipe Balbi <balbi@ti.com>
To: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Balbi, Felipe" <balbi@ti.com>
Subject: Re: [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support
Date: Mon, 3 Jan 2011 22:44:17 +0200 [thread overview]
Message-ID: <20110103204416.GA2240@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404BD3F2C58@dbde02.ent.ti.com>
Hi,
On Mon, Jan 03, 2011 at 10:45:35PM +0530, Gupta, Ajay Kumar wrote:
>> > Moreover, even Felipe also seems to move other musb
>> > DMAs (Inventra, CPPI3.0, TUSB) to drivers/dma.
>>
>> Frankly speaking, I doubt that drivers/dma/ will have place for the
>> purely MUSB specific DMA engines such as the named ones (there's no TUSB
>> DMA BTW it uses OMAP DMA).
>I think we will get more clarity once we start on this activity.
I agree, but I personally don't see that many limiting factors.
dmaengine is just a generic API for doing DMA transfers. If it's not
enough for us currently, we extend it.
--
balbi
next prev parent reply other threads:[~2011-01-03 20:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201005152214.53993.sshtylyov@ru.mvista.com>
[not found] ` <4D21F3F2.6090302@mvista.com>
2011-01-03 16:34 ` [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support Russell King - ARM Linux
2011-01-03 17:01 ` Gupta, Ajay Kumar
2011-01-03 17:07 ` Sergei Shtylyov
[not found] ` <4D220246.5020303-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2011-01-03 17:15 ` Gupta, Ajay Kumar
2011-01-03 20:44 ` Felipe Balbi [this message]
2011-01-04 13:06 ` Sergei Shtylyov
2011-01-04 14:06 ` Felipe Balbi
2011-01-04 14:40 ` Ming Lei
2011-01-04 14:56 ` Felipe Balbi
2011-01-04 15:41 ` Ming Lei
2011-01-04 18:42 ` Felipe Balbi
2011-01-04 18:50 ` Sergei Shtylyov
2011-01-04 16:37 ` Sergei Shtylyov
2011-01-05 22:03 ` Russell King - ARM Linux
2011-01-03 17:19 ` Russell King - ARM Linux
2011-01-03 20:49 ` Felipe Balbi
2011-01-04 19:12 ` Tony Lindgren
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=20110103204416.GA2240@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=ajay.gupta@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sshtylyov@mvista.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