Hi Arnd, On Sat, Dec 21, 2013 at 12:11 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Saturday 21 December 2013, Ravi Patel wrote: >> This patch adds support for APM X-Gene SoC Queue Manager/Traffic Manager. >> QMTM is required by APM X-Gene SoC Ethernet, PktDMA (XOR Engine) and >> Security Engine subsystems. All subsystems communicate with QMTM using >> messages which include information about the work to be performed and >> the location of associated data buffers. > > Please describe here what the purpose of the qmtm is, as this is not > entirely clear from the code. > > In particular, please describe how this differs from a dmaengine driver > and why it is not possible to extend the dma slave API to describe qmtm > as a dma engine. > [Loc Ho] If the QM driver implements the DMA API, what about the actual DMA engine driver which interfaces with this QM driver. We would have DMA client interfaces with the X-Gene DMA driver (not available yet) via DMA API which in turn interfaces with this QM driver via DMA API. Won't this be kind of awkward? Also, the QM only manage messages (or descriptors) which are 32-bytes or 64-bytes. It doesn't actually do any data transfer of various sizes. -Loc -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
