From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support
Date: Tue, 28 Sep 2010 14:13:19 +0400 [thread overview]
Message-ID: <4CA1BFBF.2090102@mvista.com> (raw)
In-Reply-To: <AANLkTinuQsSP1EHWn5DS_9PMrsgj+fpjLOOkpnnBaf8Q@mail.gmail.com>
Hello.
On 28-09-2010 13:13, Linus Walleij wrote:
>> Add support for Texas Instuments Communication Port Programming Interface 4.1
>> (CPPI 4.1) used on OMAP-L1x/DA8xx and AM35x.
> Sorry for late feedback ...
>> +++ linux-davinci/arch/arm/common/cppi41.c
> Can you migrate this driver to drivers/dma/cppi41.c and use the
> DMAengine interface like so many DMA drivers we have created
> recently, or is there some very special characteristics about this
> DMA controller meriting it to be placed in arch/arm/*?
I have once studied the possibility of doing this driver under
drivers/dma/, and found that hardly achievable. Maybe I should try again though...
> Yours,
> Linus Walleij
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
linux-arm-kernel@lists.infradead.org,
davinci-linux-open-source@linux.davincidsp.com,
khilman@deeprootsystems.com, linux@arm.linux.org.uk,
linux kernel <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support
Date: Tue, 28 Sep 2010 14:13:19 +0400 [thread overview]
Message-ID: <4CA1BFBF.2090102@mvista.com> (raw)
In-Reply-To: <AANLkTinuQsSP1EHWn5DS_9PMrsgj+fpjLOOkpnnBaf8Q@mail.gmail.com>
Hello.
On 28-09-2010 13:13, Linus Walleij wrote:
>> Add support for Texas Instuments Communication Port Programming Interface 4.1
>> (CPPI 4.1) used on OMAP-L1x/DA8xx and AM35x.
> Sorry for late feedback ...
>> +++ linux-davinci/arch/arm/common/cppi41.c
> Can you migrate this driver to drivers/dma/cppi41.c and use the
> DMAengine interface like so many DMA drivers we have created
> recently, or is there some very special characteristics about this
> DMA controller meriting it to be placed in arch/arm/*?
I have once studied the possibility of doing this driver under
drivers/dma/, and found that hardly achievable. Maybe I should try again though...
> Yours,
> Linus Walleij
WBR, Sergei
next prev parent reply other threads:[~2010-09-28 10:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 18:14 [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support Sergei Shtylyov
2010-05-28 20:55 ` Sergei Shtylyov
2010-09-28 9:13 ` Linus Walleij
2010-09-28 9:13 ` Linus Walleij
2010-09-28 10:13 ` Sergei Shtylyov [this message]
2010-09-28 10:13 ` Sergei Shtylyov
2011-01-03 16:06 ` Sergei Shtylyov
2011-01-03 16:34 ` Russell King - ARM Linux
2011-01-03 16:34 ` Russell King - ARM Linux
2011-01-03 17:01 ` Gupta, Ajay Kumar
2011-01-03 17:01 ` Gupta, Ajay Kumar
2011-01-03 17:07 ` Sergei Shtylyov
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 17:15 ` Gupta, Ajay Kumar
2011-01-03 20:44 ` Felipe Balbi
2011-01-03 20:44 ` Felipe Balbi
2011-01-04 13:06 ` Sergei Shtylyov
2011-01-04 13:06 ` Sergei Shtylyov
2011-01-04 14:06 ` Felipe Balbi
2011-01-04 14:06 ` Felipe Balbi
2011-01-04 14:40 ` Ming Lei
2011-01-04 14:40 ` Ming Lei
2011-01-04 14:56 ` Felipe Balbi
2011-01-04 14:56 ` Felipe Balbi
2011-01-04 15:41 ` Ming Lei
2011-01-04 15:41 ` Ming Lei
2011-01-04 18:42 ` Felipe Balbi
2011-01-04 18:42 ` Felipe Balbi
2011-01-04 18:50 ` Sergei Shtylyov
2011-01-04 18:50 ` Sergei Shtylyov
2011-01-04 16:37 ` Sergei Shtylyov
2011-01-04 16:37 ` Sergei Shtylyov
2011-01-05 22:03 ` Russell King - ARM Linux
2011-01-05 22:03 ` Russell King - ARM Linux
2011-01-03 17:19 ` Russell King - ARM Linux
2011-01-03 17:19 ` Russell King - ARM Linux
2011-01-03 20:49 ` Felipe Balbi
2011-01-03 20:49 ` Felipe Balbi
2011-01-04 19:12 ` Tony Lindgren
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=4CA1BFBF.2090102@mvista.com \
--to=sshtylyov@mvista.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.