public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sergei Shtylyov <sshtylyov@mvista.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support
Date: Mon, 3 Jan 2011 16:34:47 +0000	[thread overview]
Message-ID: <20110103163447.GB2911@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D21F3F2.6090302@mvista.com>

On Mon, Jan 03, 2011 at 07:06:10PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 15-05-2010 22:14, Sergei Shtylyov wrote:
>
>> Add support for Texas Instuments Communication Port Programming Interface 4.1
>> (CPPI 4.1) used on OMAP-L1x/DA8xx and AM35x.
>
>> At this moment, only the DMA controller and queue manager are supported.
>> Support for the buffer manager is lacking but these chips don't have it anyway.
>
>> Signed-off-by: Sergei Shtylyov<sshtylyov@ru.mvista.com>
>> Signed-off-by: Sekhar Nori<nsekhar@ti.com>
>
>    Russell, you have recently discarded this patch from your patch 
> system. Can we know the reason?

It was recently discussed with TI, and various people raised concerns
about it.  I don't remember the exact details, and I wish they'd raise
them with the patch author directly.  It may have been that it's
inventing its own API rather than using something like the DMA engine
API.

Adding linux-omap to try to get a response there.

       reply	other threads:[~2011-01-03 16:34 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   ` Russell King - ARM Linux [this message]
2011-01-03 17:01     ` [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support 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
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=20110103163447.GB2911@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --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