public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: balbi@ti.com
Cc: Ming Lei <tom.leiming@gmail.com>,
	Felipe Balbi <me@felipebalbi.com>,
	"Gupta, Ajay Kumar" <ajay.gupta@ti.com>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/3] ARM: add CPPI 4.1 DMA support
Date: Tue, 04 Jan 2011 21:50:43 +0300	[thread overview]
Message-ID: <4D236C03.9040707@mvista.com> (raw)
In-Reply-To: <20110104184244.GC2647@legolas.emea.dhcp.ti.com>

Hello.

Felipe Balbi wrote:

> On Tue, Jan 04, 2011 at 11:41:05PM +0800, Ming Lei wrote:
>> OMAP GPIOs have many usages or use cases, so we can use gpiolib
>> to simplify access to GPIOs.  If GPIOs has only one usage or use case,
>> it is not necessary to access GPIOs by gpiolib.

>> Now this kind of DMA controllers are only used by MUSB or only for
>> MUSB, so it doesn't matter to access them by dmaengine or not.

> Not entirely true. TUSB uses OMAP system DMA and AFAICT CPPI is used
> also for ethernet.

    Yes, but the CPPI registers are not compatible between MUSB and EMAC, only 
the descriptors are, AFAIK.

WBR, Sergei

  reply	other threads:[~2011-01-04 18:52 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
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 [this message]
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=4D236C03.9040707@mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=ajay.gupta@ti.com \
    --cc=balbi@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=me@felipebalbi.com \
    --cc=tom.leiming@gmail.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