2010/10/27 Ming Lei <tom.leiming@xxxxxxxxx>: > Hi Gadiyar, > > Thanks for your reply. > > 2010/10/27 Gadiyar, Anand <gadiyar@xxxxxx>: >> On Wed, Oct 27, 2010 at 5:54 AM, Ming Lei <tom.leiming@xxxxxxxxx> wrote: >>> I want to know which type of DMA is taken by musb of DM3730, >>> INVENTRA_DMA, TI_CPPI_DMA or others? >> >> Inventra DMA. An updated version compared to the OMAP34xx/35xx. >> >> - No major change to the programming model >> - The simultaneous TX-RX DMA hang bug is gone with this one. > > I find one issue about the dma transfer if Inventra DMA is used, seems > always 2 bytes less than required length, is it caused by unaligned > destination address? > > See the log captured in g_ether context: > > ...... > musb_g_rx 765: <== ep1out, rxcsr 0003 (dma) dec241c0 > dma_channel_program 165: ep1-Rx pkt_sz 512, dma_addr 0x9ecc7802 length > 70, mode 0 > configure_channel 130: dec57068, pkt_sz 512, addr 0x9ecc7802, len 70, mode 0 > dma_controller_irq 302: ch dec57068, 0x9ecc7802 -> 0x9ecc7846 (68 / > 70) => reconfig 0 > musb_g_rx 765: <== ep1out, rxcsr 2003 (dma) dec241c0 > musb_g_rx 808: RXCSR1 0003, dma off, 0003, len 68, req dec241c0 > musb_g_giveback 143: ep1out done request dec241c0, 68/1536 > musb_gadget_queue 1146: <== to ep1out request=dec241c0 > musb_interrupt 1594: ** IRQ peripheral usb0008 tx0000 rx0002 > musb_stage0_irq 462: <== Power=f0, DevCtl=99, int_usb=0x8 > musb_g_rx 765: <== ep1out, rxcsr 0003 (dma) dec244c0 > dma_channel_program 165: ep1-Rx pkt_sz 512, dma_addr 0x9ecc7002 length > 341, mode 0 > configure_channel 130: dec57068, pkt_sz 512, addr 0x9ecc7002, len 341, mode 0 > dma_controller_irq 302: ch dec57068, 0x9ecc7002 -> 0x9ecc7155 (339 / > 341) => reconfig 0 > ...... BTW: No such issue in omap3530 of beagle B5, but find it in DM3730 of beagle xM with the same musb driver and kernel. -- Lei Ming -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
