Documentation: dt: soc: add Keystone Navigator DMA bindings
authorSantosh Shilimkar <santosh.shilimkar@ti.com>
Sun, 30 Mar 2014 21:29:04 +0000 (17:29 -0400)
committerSantosh Shilimkar <santosh.shilimkar@ti.com>
Wed, 24 Sep 2014 13:49:15 +0000 (09:49 -0400)
commit8172296d8717be1951da4bb4feb2700a60e8cdde
tree2f72cc61653022a42ce901ff7e3450abfbf999c5
parent41f93af900a20d1a0a358b522b5129c89677e9dc
Documentation: dt: soc: add Keystone Navigator DMA bindings

The Keystone Navigator DMA driver sets up the dma channels and flows for
the QMSS(Queue Manager SubSystem) who triggers the actual data movements
across clients using destination queues. Every client modules like
NETCP(Network Coprocessor), SRIO(Serial Rapid IO) and CRYPTO
Engines has its own instance of packet dma hardware. QMSS has also
an internal packet DMA module which is used as an infrastructure
DMA with zero copy.

Initially this driver was proposed as DMA engine driver but since the
hardware is not typical DMA engine and hence doesn't comply with typical
DMA engine driver needs, that approach was naked. Link to that
discussion -
https://lkml.org/lkml/2014/3/18/340

As aligned, now we pair the Navigator DMA with its companion Navigator
QMSS subsystem driver.

Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kumar Gala <galak@codeaurora.org>
Cc: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Grant Likely <grant.likely@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Sandeep Nair <sandeep_n@ti.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Documentation/devicetree/bindings/soc/ti/keystone-navigator-dma.txt [new file with mode: 0644]