Heikki, What advantages does a qtd implementation provide over the existing qh based implementation? Mentor controller supports only a fixed number of ep's unlinke EHCI and I feel that it is better to have the implementation reflect it rather than attempting to make an EHCI out of Mentor. Regards swami -----Original Message----- From: linux-usb-owner@xxxxxxxxxxxxxxx [mailto:linux-usb-owner@xxxxxxxxxxxxxxx] On Behalf Of Krogerus Heikki (EXT-Teleca/Helsinki) Sent: Friday, December 18, 2009 7:14 PM To: Gupta, Ajay Kumar Cc: linux-usb@xxxxxxxxxxxxxxx; Balbi Felipe (Nokia-D/Helsinki); dbrownell@xxxxxxxxxxxxxxxxxxxxx Subject: Re: [RFC/PATCH 0/5] musb: host: mode1 support ext Gupta, Ajay Kumar wrote: >> I have only tested these with the Inventra DMA engine. >> >> Felipe Balbi (1): >> usb: musb: host: remove dma support >> >> Heikki Krogerus (5): >> usb: musb: host: transfer queue for every endpoint >> usb: musb: host: add start_dma() stop_dma() >> usb: musb: host: enable DMA for RX >> usb: musb: host: enable DMA for TX >> > > Can't we support Mode-1 with existing implementation? Do we have any > Other advantage of using the new DMA implementation? > > As you said it's tested only against Inventra DMA so we really need > time to regress test non-Inventra DMAs. For the Inventra DMA engine, mode1 Rx support was only partial, and more or less broken. I would assume the transfer queues are useful in any case. -- heikki -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
