From: Sergei Shtylyov <sshtylyov@mvista.com>
To: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pasupathy, Visuvanadan" <vichu@ti.com>,
"Balbi, Felipe" <balbi@ti.com>
Subject: Re: RFC: usb: musb: Changes proposed for adding CPPI4.1 DMA
Date: Fri, 27 Jan 2012 19:09:27 +0300 [thread overview]
Message-ID: <4F22CC37.8010307@mvista.com> (raw)
In-Reply-To: <47CEF8C4B26E8C44B22B028A650E0EA9317C5B92@DBDE01.ent.ti.com>
Hello.
On 01/25/2012 06:22 PM, Gupta, Ajay Kumar wrote:
> As a next step to dma-engine based cppi4.1 driver implementation
> this RFC has the overview of changes in the musb driver.
> RFC on CPPI slave driver changes will follow next.
> Overview of changes in the musb driver
> ======================================
> 1)Add a dma-engine.c file in the drivers/usb/musb folder
> 2)This file will host the current musb dma APIs and translates them to
> dmaengine APIs.
> 3)This will help to keep the changes in drivers/usb/musb/musb* files
> minimal and also to retain compatibility other DMA (Mentor etc.)
> drivers which are yet to be moved to drivers/dma
> 4)drivers/usb/musb/dma-engine.c, will wrap the dmaengine APIs to
> make existing musb APIs compatible.
> 5)drivers/usb/musb/dma-engine.c file will implement the filter
> functions and also implement .dma_controller_create (allocates
> & provides "dma_controller" object) and .dma_controller_delete
> 6)CPPI4.1 DMA specific queue and buffer management will be internal
> to slave CPPI DMA driver implementation.
You mean drivers/dma/ driver? I think you are forgotting that CPPI 4.1 MUSB
has some registers controlling DMA/interrupts beside those of CPPI 4.1
controller and MUSB core itself. How do they fit in your scheme?
WBR, Sergei
next prev parent reply other threads:[~2012-01-27 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 15:22 RFC: usb: musb: Changes proposed for adding CPPI4.1 DMA Gupta, Ajay Kumar
2012-01-26 9:02 ` Felipe Balbi
2012-01-27 15:01 ` Gupta, Ajay Kumar
2012-01-27 16:09 ` Sergei Shtylyov [this message]
2012-01-31 4:41 ` Gupta, Ajay Kumar
2012-01-31 11:27 ` Sergei Shtylyov
2012-02-02 4:57 ` Gupta, Ajay Kumar
2012-02-02 9:09 ` Felipe Balbi
2012-02-02 11:12 ` Sergei Shtylyov
2012-02-02 11:49 ` Felipe Balbi
2012-02-02 12:02 ` Sergei Shtylyov
2012-02-02 12:15 ` Felipe Balbi
2012-02-02 11:05 ` Sergei Shtylyov
2012-02-03 8:42 ` 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=4F22CC37.8010307@mvista.com \
--to=sshtylyov@mvista.com \
--cc=ajay.gupta@ti.com \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=vichu@ti.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 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.