Texas Instruments CPPI 4.1 DMA support for the MUSBMHRDC driver.
The code makes use of the accelerated "generic RNDIS" DMA mode, falling back to
the transparent (packet per transfer) mode if the hardware restrictions prevent
it from using the accelerated mode.
---
Changes since the previous take:
Sergei Shtylyov wrote:
Texas Instruments CPPI 4.1 DMA support for the MUSBMHRDC driver.
..
Index: linux-davinci/drivers/usb/musb/Makefile
===
--- linux-davinci.orig/drivers/usb/musb/Makefile
+++ linux-davinci/drivers/usb/musb/Makefi
Hello.
stanley.miao wrote:
Texas Instruments CPPI 4.1 DMA support for the MUSBMHRDC driver.
..
Index: linux-davinci/drivers/usb/musb/Makefile
===
--- linux-davinci.orig/drivers/usb/musb/Makefile
+++ linux-davinci/drivers/usb/musb/
Have you tested USB gathet Ethernet ?
It works when MUSB_PIO_ONLY is enabled.
When USB_TI_CPPI41_DMA is enabled, it is able receive data, but isn't
able to transfer data.
Stanley.
Sergei Shtylyov wrote:
Hello.
stanley.miao wrote:
Texas Instruments CPPI 4.1 DMA support for the MUSBMHRDC dr
Hello.
stanley.miao wrote:
Sorry about the late reply, I guess I've forgotten about your mail.
Have you tested USB gathet Ethernet ?
Yes, but only in the internal tree (of different version). If you mean
gadget Ethernet. :-)
It works when MUSB_PIO_ONLY is enabled.
When USB_TI_CPPI4
Hello.
Gupta, Ajay Kumar wrote:
Sergei,
Is there any other update to this patch ?
The last was take 5 from August 21th:
http://marc.info/?l=linux-usb&m=125087318308323
> We have some patches on top of your base version.
Interesting...
Kevin and David,
There is another TI platfor
@linux.davincidsp.com; stanley.miao; Hilman, Kevin; david-
> b...@pacbell.net; Subbrathnam, Swaminathan; linux-arm-
> ker...@lists.infradead.org
> Subject: RE: [PATCH RFC 1/2] MUSB: CPPI 4.1 DMA driver (take 4)
>
> > -Original Message-
> > From: Sergei Shtylyov [mailto
> On Mon, Nov 02, 2009 at 09:51:13AM +0530, Gupta, Ajay Kumar wrote:
> > Is there any updated patch on cppi4.1 core also?
>
> Is there _any_ cppi4.1 core patch anywhere? Not according to google.
Russell,
Here is the latest version of cppi4.1 core.
http://patchwork.kernel.org/patch/46698/
> >
> > Here is the latest version of cppi4.1 core.
> > http://patchwork.kernel.org/patch/46698/
>
> A few points come up about this.
>
> 1. alloc_queue() - this is a find_next_zero_bit loop coupled with a
>check for the excluded bitmap.
>
> end = start + count;
> do {
>
> > 3. linking_ram - cppi41_queue_mgr_init() seems to be the only user. I
> >don't see why linking_ram would be necessary.
> >
> > 4. debugging printks via pr_debug() please (and define DEBUG at the top
> of
> >the file to enable debugging.)
>
> Thanks for the review and valuable comments
Hello.
Gupta, Ajay Kumar wrote:
4. debugging printks via pr_debug() please (and define DEBUG at the top of
the file to enable debugging.)
That's been already done in the recent version of the patch.
Thanks for the review and valuable comments.
As we have to change the cu
Hello.
Gupta, Ajay Kumar wrote:
Is there any updated patch on cppi4.1 core also?
Is there _any_ cppi4.1 core patch anywhere? Not according to google.
Russell,
Here is the latest version of cppi4.1 core.
http://patchwork.kernel.org/patch/46698/
Again, it's not the latest
12 matches
Mail list logo
