All of lore.kernel.org
 help / color / mirror / Atom feed
From: felipe.balbi@nokia.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 1/2] MUSB: CPPI 4.1 DMA driver (take 4)
Date: Mon, 2 Nov 2009 13:38:37 +0200	[thread overview]
Message-ID: <20091102113836.GH9446@nokia.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E73940436EEB601@dbde02.ent.ti.com>

On Mon, Nov 02, 2009 at 12:24:00PM +0100, ext Gupta, Ajay Kumar wrote:
> > >
> > > > If it's a USB DMA device (from the patches I can find, that seems to
> > be
> > > > the case) then why can't it live in drivers/usb or drivers/dma ?
> > >
> > > CPPI4.1 DMA engine can be used either by USB or by Ethernet interface
> > though
> > > currently only USB is using it but in future even Ethernet devices may
> > use it.
> > >
> > > Infact, there is a TI platform (not in mainline), where both USB and
> > Ethernet interface is using CPPI4.1 DMA.
> > 
> > you might want to provide support for it via drivers/dma and for the
> > musb stuff, you just add the wrappers musb uses. See how tusb6010_omap.c
> > uses OMAP's system dma which is also used by any other driver which
> > requests a dma channel.
> 
> Sounds good. 
> 
> So if we want to move CPPI4.1 DMA core to drivers/dma then it has to follow
> standard set of DMA APIs (right?), which I afraid, may not be done in current implementation.

yes, if it's not done right now, it has to be done.

-- 
balbi

  reply	other threads:[~2009-11-02 11:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200908142241.00528.sshtylyov@ru.mvista.com>
     [not found] ` <4A8A202E.2040505@windriver.com>
     [not found]   ` <4A8A7047.9080405@ru.mvista.com>
     [not found]     ` <4A8CF552.3080801@windriver.com>
     [not found]       ` <19F8576C6E063C45BE387C64729E73940436EEAE36@dbde02.ent.ti.com>
     [not found]         ` <4AE85B02.1080207@ru.mvista.com>
2009-10-28 15:18           ` [PATCH RFC 1/2] MUSB: CPPI 4.1 DMA driver (take 4) Gupta, Ajay Kumar
2009-11-02  4:21             ` Gupta, Ajay Kumar
2009-11-02 10:37               ` Russell King - ARM Linux
2009-11-02 10:57                 ` Gupta, Ajay Kumar
2009-11-02 11:02                   ` Felipe Balbi
2009-11-02 11:24                     ` Gupta, Ajay Kumar
2009-11-02 11:38                       ` Felipe Balbi [this message]
2009-11-02 11:54                   ` Russell King - ARM Linux
2009-11-04  3:54                     ` Gupta, Ajay Kumar
2009-11-06  3:45                       ` Gupta, Ajay Kumar
     [not found]                     ` <4B0ED746.1040201@ru.mvista.com>
2009-11-27  2:37                       ` Subbrathnam, Swaminathan
     [not found] <19F8576C6E063C45BE387C64729E7394044A2779F5@dbde02.ent.ti.com>
2009-12-29  8:43 ` Gupta, Ajay Kumar
2009-12-29 12:54   ` Felipe Balbi
2009-12-30  3:46     ` Subbrathnam, Swaminathan
2009-12-30 12:24       ` Felipe Balbi
2009-12-30 13:02         ` Subbrathnam, Swaminathan
     [not found]         ` <4B3B5232.5030804@ru.mvista.com>
2009-12-30 13:22           ` Felipe Balbi
     [not found]             ` <19F8576C6E063C45BE387C64729E7394044A96D44E@dbde02.ent.ti.com>
2010-02-10  6:46               ` Gupta, Ajay Kumar

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=20091102113836.GH9446@nokia.com \
    --to=felipe.balbi@nokia.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.